Sounds like Digital Ocean was the problem, not Kubernetes.
Been running managed Kubernetes in GCP for years without any issues.
They are bugging me to update for some time now, but I don't think they would force an update on me.
Been running managed Kubernetes in GCP for years without any issues.
They are bugging me to update for some time now, but I don't think they would force an update on me.
I once tried nomad because it claimed to be simpler. I stopped when I realized I’d also have to use multiple clusters to run a cluster (nomad+consul).
I use k3s because I build apps for multiple clients and I like the flexibility that it gives me in running servers like cattle.
My point is that these orchestrators need to start decreasing the enormous amount of risk they add to any project.
If you want a Kubernetes cluster that never gets forcibly updated or shut down, you should not be using a managed service, period.
How do they test that across the infinite number of permutations of configurations and deployments of K8S in the field though? It'll work for some people on the happy path, but it's really hard to maintain over time. Worse, it'll break randomly at some point in the future that is hard to predict, instead of at some publicly announced point in time where the breaking change is deployed (how it happened this time).