|
|
|
|
|
|
by SOLAR_FIELDS
588 days ago
|
|
|
You have to link a card if you don’t want to have a bot that spams looking for open instances. I tried without linking a card but it’s basically impossible without automation to secure an instance, and they can arbitrarily just nuke your instance at any time if they feel like you are being “abusive” or even just idling the machines and not using resources, plenty of complaints about that. Adding a card removes all of those concerns and you can instantly provision the resources and never worry about anything being arbitrarily shut down. I have only had one 1 cent charge since I got it because I provisioned some volume storage before I realized that it would incur costs. If you just use the repo I linked and otherwise never touch resources or auto provision anything on the infra side you’ll never be charged. I would highly recommend this use case for learning kube, but also it’s kind of limiting because several things you might want to use with kube will also incur additional costs. You can avoid the costs if you simply just don’t do anything that triggers a cost event, but people who are not familiar with how kube can provision infra resources under the hood might footgun themselves and wire into a cloud load balancer instead of using MetalLB for instance. Probably inference is not really a good use case here, the compute they give is considered extremely good in terms of free, but still kind of anemic for inference use cases. |
|
|
I only run the tiny models for fun (the CPU inference is enough) and any complex coding tasks go through GPT or Claude. Mainly just using the one instance as another backup server, run scrapers, host a bunch of containers, and experiment with networking services. I don't see a reason to split up my one instance, but maybe in the future.