3 ms·

k8s is a complex solution for complex problems. You don't need k8s to host landing or personal blog type of service. Once you move to a type of project with co

k8s is a complex solution for complex problems. You don't need k8s to host landing or personal blog type of service. Once you move to a type of project with complex demands around deployments, log management, failover management, secrets, environments, resource isolation, etc., then building something to solve this set of problems over and over again is very expensive when off-the-shelf battle-tested solution is available.

sureglymop 3y ago
What about using docker swarm or even a single node docker swarm cluster? I think that could be a viable alternative for small stuff.
- SirensOfTitan 3y ago
  The thing is, k8s has a lot of mindshare. It's entirely easier to go and find some pertinent issue with your k8s set-up through a simple search, whereas e.g. nomad and swarm have much less mindshare. You don't have to go full complexity with k8s. You can just use a managed k8s provider and ship a simple deployment with an anti-affinity policy to distribute across VMs on creation. Sure, there are other solutions [and this one is likely to not be the cheapest], but they're all vendor locked--k8s is about as close to a cloud agnostic compute as we're likely to get.
- achempion 3y ago
  I enjoy docker swarm for small hobby projects. It's simple and easy to maintain if you want to benefit from container apps and configuration. Once your service grows, you'll notice some rough edges around the docker swarm. When you start having dedicated SRE/DevOps roles, moving from heroku/swarm to k8s will make sense.
lakomen 3y ago
The arrogance of you. You can do more on a single server than hosting "landing pages" or "personal blog". I host seemingly complex projects with simple methods, without needing any complex k8s crap. That's what you people aren't getting. You're so full into the complexity that you don't see the simple solution as something worthwhile. WHAT about k8s is more battle tested than decades of doing the simple and efficient on a 1-3 servers? You're brainwashed. Possibly even a shill of one of those expensive cloud providers.

sureglymop 3y ago

What about using docker swarm or even a single node docker swarm cluster? I think that could be a viable alternative for small stuff.

SirensOfTitan 3y ago
The thing is, k8s has a lot of mindshare. It's entirely easier to go and find some pertinent issue with your k8s set-up through a simple search, whereas e.g. nomad and swarm have much less mindshare. You don't have to go full complexity with k8s. You can just use a managed k8s provider and ship a simple deployment with an anti-affinity policy to distribute across VMs on creation. Sure, there are other solutions [and this one is likely to not be the cheapest], but they're all vendor locked--k8s is about as close to a cloud agnostic compute as we're likely to get.
achempion 3y ago
I enjoy docker swarm for small hobby projects. It's simple and easy to maintain if you want to benefit from container apps and configuration. Once your service grows, you'll notice some rough edges around the docker swarm. When you start having dedicated SRE/DevOps roles, moving from heroku/swarm to k8s will make sense.

lakomen 3y ago

The arrogance of you. You can do more on a single server than hosting "landing pages" or "personal blog". I host seemingly complex projects with simple methods, without needing any complex k8s crap. That's what you people aren't getting. You're so full into the complexity that you don't see the simple solution as something worthwhile. WHAT about k8s is more battle tested than decades of doing the simple and efficient on a 1-3 servers? You're brainwashed. Possibly even a shill of one of those expensive cloud providers.