Re:Ask HN: In a microservice architecture, how do you handle...
by ibotty on Thursday January 21, 2016 @08:20AM
(#10944973)
afaik the only part of kubernetes accessing etcd is the master. Nodes don't need and can't access etcd directly.
That still leaves the secret in plain view on the nodes that run the pod that needs the service. It would be great to be able to umount the secret when not needed anymore.
Re:Ask HN: In a microservice architecture, how do you handle...
by theptip on Friday January 22, 2016 @12:21AM
(#10950917)
Correct, the etcd instance is only accessed by the master, which uses etcd to back the apiserver. But any root process on the nodes can access the secrets through the apiserver (there's no access control at this point).
Also on access control, any process with root on any node in your cluster can get access to all your secrets (since the kubelet needs to be able to do so). There are no user access controls either; any cluster admin can dump all the secrets.
This stuff is clearly documented, so it's not an indictment on k8s; I just get the feeling that the feature isn't really ready for production use yet.