39 ms·

$1,000/yr is definitely excessive. You can have managed Kubernetes for ~ $100/yr from Google or (recently) Digital Ocean using smaller instance types. The poin

$1,000/yr is definitely excessive. You can have managed Kubernetes for ~ $100/yr from Google or (recently) Digital Ocean using smaller instance types. The point about maintenance is a good one if you're running purely static sites. K8s has a steep learning curve, though FWIW I think its probably easier than systemd and standard unix administration + puppet/chef/ansible/etc.

Spartan-S63 7y ago
For sure. $1000/yr is excessive. For a third the cost, you can have a three node, small cluster on DO that you can experiment with. I did it prior and will probably do it again in the future when I have something worth hosting out on the web. I agree with your second point, too. If you don't view K8s as something you need to know _everything_ about, it's a powerful tool that simplifies things that you'd need multiple tools for. I never really learned provisioning tools like Puppet/Chef/Ansible and Systemd, so k8s was a fresh experience for me. I like it, though, because I really like containers over VMs as the unit that's running my code.
- sombremesa 7y ago
  GKE is cheaper than DO if you don't have huge cpu needs, I just checked it recently. DO minimum is $15/mo for kubernetes, on Google you can get to around $7 with a "micro" VM. That is, if you really want managed kubernetes. Otherwise you can get a $5 VM on DO.
raverbashing 7y ago
I'd say it's debatable if it's really easier than puppet/chef/systemd For something really simple, sure. For something that goes beyond a simple web server, you might be touching on similar competencies to those needed to run your services "the old way" It might be easier to manage, sure, but to get started, and have an efficient deployment, not necessarily Examples: your system needs a special service or library that is not available in the distro, you need to deploy a cronjob or similar periodic service, you need multiple services running at the same time (either in the same pod or separately), etc

Spartan-S63 7y ago

For sure. $1000/yr is excessive. For a third the cost, you can have a three node, small cluster on DO that you can experiment with. I did it prior and will probably do it again in the future when I have something worth hosting out on the web. I agree with your second point, too. If you don't view K8s as something you need to know _everything_ about, it's a powerful tool that simplifies things that you'd need multiple tools for. I never really learned provisioning tools like Puppet/Chef/Ansible and Systemd, so k8s was a fresh experience for me. I like it, though, because I really like containers over VMs as the unit that's running my code.

sombremesa 7y ago
GKE is cheaper than DO if you don't have huge cpu needs, I just checked it recently. DO minimum is $15/mo for kubernetes, on Google you can get to around $7 with a "micro" VM. That is, if you really want managed kubernetes. Otherwise you can get a $5 VM on DO.

raverbashing 7y ago

I'd say it's debatable if it's really easier than puppet/chef/systemd For something really simple, sure. For something that goes beyond a simple web server, you might be touching on similar competencies to those needed to run your services "the old way" It might be easier to manage, sure, but to get started, and have an efficient deployment, not necessarily Examples: your system needs a special service or library that is not available in the distro, you need to deploy a cronjob or similar periodic service, you need multiple services running at the same time (either in the same pod or separately), etc