Someone hating on kubernetes and cobbling together their own stuff that "does the same, but simpler". Usually only simpler for that person.
Ask HN: What is your Kubernetes nightmare?
31–40 of 263 posts
Re: Ask HN: What is your Kubernetes nightmare?
#32Honestly, creating my first K8s deployment of a service; typing out at least 150 lines of YAML to define my Deployment, figuring out how my ConfigMaps, Secrets, and Volumes, Services are defined and connected together. Vanilla K8s YAML is extremely low-level.
I'm buried up to my balls in this right now. My favourite part is nested 'spec' objects where I've no clear view into what each spec is.
Re: Ask HN: What is your Kubernetes nightmare?
#33Storage:
Shared FS between nodes, autoscaling volume claim sizes, autoscaling volume claim iops, and measuring storage utilisation (iops e.g.) for pod/node/pv.
How have I solved it? I haven't and I know its a key part of cost-control for us in about 12 months.
Fast deploy:
I'm trying to get a test cluster up in less than half an hour. With the DAG for building it all I'm getting a failure rate of 30% if I don't leave arbitrary timings and extra steps. I've also only automated about 25% of our stuff, so I expect it will take longer.
Re: Ask HN: What is your Kubernetes nightmare?
#34- 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
Re: Ask HN: What is your Kubernetes nightmare?
#35I honestly kinda like kubernetes and I have no problem tying together a bunch of distributed resources in my head.
The biggest nightmare for me is networking, simply because I'm not trained in networking. I know the basics to become a senior sysadmin but it's not natural to me. So mix in kubernetes and it becomes even more abstract.
Re: Ask HN: What is your Kubernetes nightmare?
#36I'm probably the wrong person to ask. My Kubernetes nightmare is having to configure anything from scratch. Or having to fix something that doesn't work.
My comfort zone is where Kubernetes works fine and I don't have to touch it, or only update trivial stuff.
Re: Ask HN: What is your Kubernetes nightmare?
#37More distributed system than Kubernetes, but quite fun : We deployed a MongoDB cluster on our Kubernetes Clusters. Our application was a having a chat feature that stored the messages into the MongoDB cluster. After some months, we realized that we got some weird issues, some messages was arriving in the wrong orders, like : 1. A : Hi ! 2. B : Bye ! See you next time ! 3. A : Great and you ? 4. B : Hello ! How are yo…
1. A : Hi !
2. B : Bye ! See you next time !
3. A : Great and you ?
4. B : Hello ! How are you ?
Re: Ask HN: What is your Kubernetes nightmare?
#38Honestly I don't get the hate k8s get. I run my own clusters and it just works. Sure I have to ignore a lot of crap in the setup phase, there are so many products out there I don't want to pay for. The nightmare may come from some devop installing a bunch of helm charts without configuring things properly. Scaling down to a minimal cluster is a real concern: I would like to run k8s for some micro project that literal…
Never in my experience when someone says it just works does it just work in reality. Usually they are hiding some things that they are keeping up with but for some reason don't include those issues as the thing not working.
Re: Ask HN: What is your Kubernetes nightmare?
#39For me the primary thing is OOM killed. But swap support is being worked on.
And then perhaps the proper handling of persistent disk.
Re: Ask HN: What is your Kubernetes nightmare?
#40The only nightmare is the same one as with npm and pip etc.: dependencies hiding behind other dependencies and having badly documented charts being used that don't share basic lifecycle information.
Kubernetes itself has always been fine, just like a bare network or bare OS has been, but when you start stacking stuff built by other people (especially when the stuff isn't of the best quality) it just goes downhill from there.
Perhaps the actual nightmare is inadequate quality control... but that's not really specific to packaging or shared components in Kubernetes.