-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CIS Benchmark Compliance - /var/lib/etcd permissions #1308
Comments
I guess that it's ok to use |
If the directory don't exist the kubelet will create it with |
From https://kubernetes.io/docs/concepts/storage/volumes/#hostpath
|
@yagonobre thanks. @raesene so, this seems as part of the k8s internals. |
Yes, let's fix this in v1.14. It might be relevant with a cherrypick, depending on the implementation. |
Easiest way forward here is to create the directory with |
this was mentioned in the k8s slack and I was asked to file an issue, so here it is :) As a little background I'm one of the authors of the CIS benchmark and I'm looking at changes we may need to make for the next version. Our reference installation mechanism is kubeadm.
At the moment a default kubeadm installation will get a failing mark on item 1.4.11 of the CIS Kubernetes Benchmark version 1.3 as the permissions on
/var/lib/etcd
are 755 rather than the recommended 700. Looking at a sample install it looked like that directory just had a single entry which was set to 700.What I wanted to check is, is there a requirement for the permissions to be 755 on that directory for operation of the cluster or could they be changed to 700?
If there's an operational requirement for those permissions, then we could look at whether it would be possible to modify the standard, but if not, it would be good to see those changed on a default install to 700.
The text was updated successfully, but these errors were encountered: