- 60% of the Kubernetes ecosystem is half-baked alpha software - Maintaining 200+ clusters for 10 small applications - Cloud bills - Autoscaling never working well - Trying to untangle Terraform state without taking down Prod
We are using karpenter.sh for autoscaling. Works just fine.
Ask HN: What is your Kubernetes nightmare?
261–263 of 263 posts
I work with the karpenter team. Glad to hear you like it. Would love it if you added your info to our public reference adopters.md file https://github.com/aws/karpenter/blob/main/ADOPTERS.md
Re: Ask HN: What is your Kubernetes nightmare?
#262Earlier quoted context omitted.
I've done exactly that. It wasn't fun. RHEL, k3s, ansible, Longhorn, metallb, to name a few. Storage is the fun part.
I was playing around with a local Elasticsearch cluster and I couldn't figure out how to "do" k8s storage. Some kind of like... shared NFS volume or something maybe? Could you spread some tips from your experiences?
We used a large amount of local physical storage spread pretty evenly over the machines in the cluster and then gave this to Longhorn to manage.
It pretty much takes care of everything else. But does require some preventative TLC
Re: Ask HN: What is your Kubernetes nightmare?
#263Earlier quoted context omitted.
And does a lot less too, since it describes single node deployment, without any complexities behind networking and communication of services on different nodes.
A docker compose file is also used for swarm mich is a multi-server deployment.
But is that a more complex file than the single node one?