6 ms·
I do have only very minimal xp in k8s, as I have tried to use it only once (and never again). To me it seem like mOst of the comments are about the unusable and
by zelphirkalt 6y ago
I do have only very minimal xp in k8s, as I have tried to use it only once (and never again). To me it seem like mOst of the comments are about the unusable and unmaintainable yaml configuration files. This seems like exactly the issue I had a few years ago, when I was cursing, because I could not find a spec or docs for the yaml stuff in all the pages and pages of seemingly important documentation and thus could not figure out how to transform a docker only deployment into k8s deployment. I also remember having to set up helm, according to whatever tutorial or official guide I was following. It was all a distant nightmare, that I do not wish to repeat.
- regularfry 6y agoThere's definitely a need for an opinionated layer over the top, with much simpler configuration. Probably more than one, with different use cases. Nobody should have to wrangle that much yaml.
- cpursley 6y agohttps://convox.com https://convox.com It's basically heroku on top of k8s and you bring your own cloud.
- louiskottmann 6y agoYou can start off with an example you would find online, then use "kubectl explain" to read about the options used and other ones you want to use.
- deleted 6y ago[deleted]
- sippeangelo 6y agoThis. I'm currently trying to figure this mess out and all I want is a reference for the different objects and what parameters they take, or what the hell an "apiVersion" is and which ones are available. Instead their "documentation" is a bunch of unhelpful guides that never show examples of what I need to know. How this has reached widespread adoption is beyond me.
- starfox64_ 6y agoI find that the best place to have an actual documentation for writing yaml files is the API Reference[0] and falling back to the "regular" documentation for more detailed explanations about specific topics. The reference lists all properties and type for everything that you can shove in your yaml files. [0] https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/ https://kubernetes.io/docs/reference/generated/kubernetes-ap...