News for hackers. Stuff that matters.
Re:Introducing Docker Secrets Management by simplehuman on Thursday February 09, 2017 @12:50PM (#13609046)
This is really nice. What is the equivalent in the kubernetes world?
Re:Introducing Docker Secrets Management by eicnix on Thursday February 09, 2017 @12:59PM (#13609146)
Kubernetes supported secrets for nearly 2 years: https://kubernetes.io/docs/user-guide/secrets/

They currently debate over pluggable secret stores: https://github.com/kubernetes/kubernetes/issues/10439

You can use Hashicorp Vault as a third party resource to store your secrets: https://github.com/Boostport/kubernetes-vault

Kubernetes also supports RBAC to control access to secrets: https://kubernetes.io/docs/admin/authorization/

Re:Introducing Docker Secrets Management by tonyhb on Thursday February 09, 2017 @01:18PM (#13609343)
Secrets as in passwords and keys stored at rest in plain text. So not really secrets.
Re:Introducing Docker Secrets Management by benth on Thursday February 09, 2017 @01:42PM (#13609589)
It's not so much the plain text part that bothers me, it's the access control.

Quoting the docs at https://kubernetes.io/docs/user-guide/secrets/#security-prop...:

"Currently, anyone with root on any node can read any secret from the apiserver, by impersonating the kubelet. It is a planned feature to only send secrets to nodes that actually require them, to restrict the impact of a root exploit on a single node."

As your cluster grows, your risk grows.