4 ms·

This guide makes an interesting choice with regards to etcd security, which I'm not sure I'd go with. etcd stores a load of sensitive cluster information, so u

This guide makes an interesting choice with regards to etcd security, which I'm not sure I'd go with. etcd stores a load of sensitive cluster information, so unauthorised access to it is a bad thing. There's an assumption in the guide that you have a "secure network" and therefore don't have to worry about etcd authentication/encryption. The thing is if you have a compromised container (say) and that container, which has an in-cluster IP address can see your etcd server, then it can easily dump the etcd database and get access to the information held in it... Personally I'd recommend setting up a small CA for etcd and using it's authentication features, there's a good guide to this on the CoreOS site https://coreos.com/etcd/docs/latest/op-guide/security.html https://coreos.com/etcd/docs/latest/op-guide/security.html

pstadler 9y ago
This is great input and definitely something worth considering. Related issue on GitHub: https://github.com/hobby-kube/guide/issues/6 https://github.com/hobby-kube/guide/issues/6
- raesene6 9y ago
  no worries, I've got some more info. on that on my blog https://raesene.github.io/blog/2017/05/01/Kubernetes-Security-etcd/ https://raesene.github.io/blog/2017/05/01/Kubernetes-Securit... which may be of use.
013a 9y ago
Is the issue you outline something an out-of-the-box Kops cluster would suffer from?
- raesene6 9y ago
  That's a very interesting question. The answer is that it depends on the K8s distribution in question. One of the challenges of K8s security is that there are a wide variety of distributions, each with their own defaults and configuration, so it's hard to make blanket statements about their security. I've definitely seen some with this issue out of the box.