4 ms·
> I say that because I've never seen a standard so easy and seamless for a developer to get his code running. You deploy using extremely long YAML files, your
by Sebb767 5y ago
> I say that because I've never seen a standard so easy and seamless for a developer to get his code running.
You deploy using extremely long YAML files, your app interacts with a lot of complex software (secret storage, ingress controller etc) and accessing your app for debugging is very non-straightforward. Once you understand the concepts and stack it's great, but when you're coming from locally running your app or even docker, it's as opaque as it gets.
In my experience, it's actually worse for developers, because infra people are forced to learn k8s as direct part of their job, while for developers it's more of a sidenote.
- tardigr8 5y agoI agree it is a steep learning curve coming from docker only. But if you have to scale your app or other resources quickly and easily, I think k8s is the best of the bunch. I have found other solutions more difficult (docker swarm, paas platforms like heroku, a custom nginx and a lot of docker hosts etc..). If you don't need that easy scaling, then I don't think there is a need for k8s.