4 ms·
I often end up referring to the GoDoc and core code when the documentation is lacking. I wish the docs gave a deeper explanation of each component and the objec
by btym 10y ago
I often end up referring to the GoDoc and core code when the documentation is lacking. I wish the docs gave a deeper explanation of each component and the object model.
There are also places where the content is too specific and not generally applicable. For example, this addon example that assumes you're using the kube-up convenience script: http://kubernetes.io/docs/getting-started-guides/logging-elasticsearch/ http://kubernetes.io/docs/getting-started-guides/logging-ela... No explanation of what the magic flag actually does, just "set this and run kube-up". (the real explanation is "copy the appropriate specs to your cluster addon directory")
- kozikow 10y agoYeah I generally look at go objects for docs. Also I think just writing configs in go rather than yaml is better. I wrote a post about it: https://kozikow.com/2016/09/02/using-go-to-autogenerate-kubernetes-configs/ https://kozikow.com/2016/09/02/using-go-to-autogenerate-kube... .
- swozey 10y agoThats for the post. I've been using k8s forever but I'm pretty new to go. It's probably a great idea to start doing things in go instead.