5 ms·
Speaking of security on Kubernetes, it's worth noting that most of the "Getting Started" guides (e.g. [0]) to help you set up a cluster result in completely una
by Veratyr 10y ago
Speaking of security on Kubernetes, it's worth noting that most of the "Getting Started" guides (e.g. [0]) to help you set up a cluster result in completely unauthenticated API servers.
This means that by default, anyone can do anything they want with your cluster.
There are no warnings, no suggestions that turning on the much better TLS based authentication would be a good idea (or even how to do it), no nothing.
Be very careful with Kubernetes.
[0]: http://kubernetes.io/docs/getting-started-guides/ubuntu/ http://kubernetes.io/docs/getting-started-guides/ubuntu/
- robszumski 10y agoMaintaining community-led documentation is a hard and time consuming process, especially with a young project. I encourage you to get involved if you have a few free cycles. Sometimes you have to take a stance on these types of things, as we have done with the CoreOS + Kubernetes community guides [0]. The guides are open source, but full TLS, passing conformance tests, etc is required for contribution. (I work at CoreOS) [0]: https://coreos.com/kubernetes/docs/latest/#installation https://coreos.com/kubernetes/docs/latest/#installation
- praneshp 10y agoThe CoreOS documentation is a lifesaver (even when setting up k8s on a non-coreOS system. Thanks a lot (and agree with the comments on documentation/involvement).