K8S Security
- Keep API Server secure from accessing by outsider
- Beware of runaway POD
- Helm tiller pod
- Validate Images (image scan, e.g coreos/clair)
For 1:
Most cloud provider's set up is fine.
For 2:
- Make sure running POD's service account has limited access to the cluster.
- Make sure with every k8s services, connect with authentication.
For 3:
- Beware the privilege granted to tiller POD. Once it's compromised, the cluster
is compromised. (Helm 3 will thus remove the use of tiller POD due to mainly the security issue)
Reference:
Creating a cluster network policy https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy
Access control overview https://cloud.google.com/kubernetes-engine/docs/concepts/access-control
Using PodSecurityPolicies https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.