Kubernetes the Hard Way
Lots of good information here but it is still not enough for a production setup IMHO.<p>There is a great need of good source of production setups. In open source software this seems to be the secret that no one is willing to reveal. I tried to setup a kubernetes cluster from scratch a while ago and soon I was browsing the source code for answers. Openstack is the same, you need to understand a lot about the inner workings before you can even attempt to setup something for production.<p>There is always a simple &quot;this shell script starts your own &lt;name your tech here&gt; cluster in vagrant&quot; but it is still not a production setup.<p>And even if this article is the &quot;hard way&quot; it describes:<p>&gt; This is being done for ease of use. In production you should strongly consider generating individual TLS certificates for each component.&quot;<p>And it does not mention that the crucial part is the common name field in the certificate maps to the user name that is the magic information that I once needed.<p>I sincerely appreciate this article but production setup is still a long learning experience away.