Why is Kubernetes adoption so hard?
plural.sh
Why is Kubernetes adoption so hard?
1–10 of 21 posts
Re: Why is Kubernetes adoption so hard?
#2This is a pure marketing high bullshit article. This is akin to spam.
Re: Why is Kubernetes adoption so hard?
#3The Kubernetes API allows you to do a hell of a lot, and people can go overboard with that (certainly I have).
Inner peace arises from looking at all of the possibility and limiting yourself to what you actually need.
Re: Why is Kubernetes adoption so hard?
#4The Kubernetes API allows you to do a hell of a lot, and people can go overboard with that (certainly I have). Inner peace arises from looking at all of the possibility and limiting yourself to what you actually need.
> Inner peace arises from looking at all of the possibility and limiting yourself to what you actually need.
Constraints are the only way you will ever escape from complexity jail.
Trouble is that some understand this equation and don't want out. Getting this stuff solved means you have to start doing actual work and dealing with customer needs again. Equity is the only thing I think can solve this at scale. There aren't many who are willing to push through "kill my ego" hell just so they can sit in line at "help the customer" hell. You need a pretty big carrot (or stick) to sell this one.
Re: Why is Kubernetes adoption so hard?
#5It feels like the article was written with the audience of business people, not ops. I asked ChatGPT what Cluster API is or what it tries to solve and it made much more sense.
Cluster API does not have an integration with Karpenter and there are more limitations [1], rendering it unusable in my use case.
Re: Why is Kubernetes adoption so hard?
#6It feels like the article was written with the audience of business people, not ops. I asked ChatGPT what Cluster API is or what it tries to solve and it made much more sense. Cluster API does not have an integration with Karpenter and there are more limitations [1], rendering it unusable in my use case. [1] https://cluster-api-aws.sigs.k8s.io/roadmap.html
[deleted]
Re: Why is Kubernetes adoption so hard?
#7Without following the link I would say because YAML.
Re: Why is Kubernetes adoption so hard?
#8Because helm charts lack a schema.
Programming by yaml configuration means you spend time searching github for an example kind of like what you're trying to do instead of having actual tools which allow auto-completion.
Editing helm charts it the ultimate form of throwing spaghetti at the wall and praying it works, without being able to actually test anything locally.
Re: Why is Kubernetes adoption so hard?
#9One of the big problems I'm having in building a bare metal cluster is the awful error messages.
The flexibility of allowing many different CRIs, CNIs and storage providers does let you find something that suits your use-case, but that generality also means the error messages can't be as specific as a fully integrated solution.
The issue is exacerbated when the OS and cluster are hardened to CIS benchmarks with policy managers - trying to figure out what is preventing your app from running and why is just so much harder than it needs to be.
Re: Why is Kubernetes adoption so hard?
#10Because helm charts lack a schema. Programming by yaml configuration means you spend time searching github for an example kind of like what you're trying to do instead of having actual tools which allow auto-completion. Editing helm charts it the ultimate form of throwing spaghetti at the wall and praying it works, without being able to actually test anything locally.
At this point, if it’s painful enough, why isn’t compiling-to-yml tools more popular?
Example: https://github.com/dhall-lang/dhall-kubernetes
Haven’t used dhall myself but I’d definitely prefer a DSL on top of yaml.