Skip to content
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

Kube-bench support for kubeadm testing #65

Open
lizrice opened this issue Nov 1, 2017 · 5 comments
Open

Kube-bench support for kubeadm testing #65

lizrice opened this issue Nov 1, 2017 · 5 comments

Comments

@lizrice
Copy link
Contributor

lizrice commented Nov 1, 2017

See discussion started under issue #56. It would be great to use kube-bench as part of kubeadm testing to ensure sensible defaults.

@lizrice
Copy link
Contributor Author

lizrice commented Nov 1, 2017

Tagging @luxas who had the original idea :-)

@luxas
Copy link

luxas commented Nov 1, 2017

Could you test to run kube-bench against a kubeadm cluster and post the results here?
I might be able to do it as well, but will be delayed a some weeks or so in that case :(

After we have the inital report for v1.8, we can see how both kube-bench and kubeadm can be improved. Eventually, as a consequence of that work, we can start automatically enforcing these test results in automated e2e tests.

Cheers, thanks for the great project!

@jaxxstorm
Copy link

@luxas just as an FYI, I'm working on securing a cluster using kube-bench and generating a kubeadm configuration file using jsonnet. The project is here: apptio/kubeadm-bootstrap#4

The complete configuration file will be here: https://github.com/apptio/kubeadm-bootstrap/blob/master/lib/kubeadm.libsonnet

This might help in future.

@robertojrojas
Copy link
Contributor

Hey @jaxxstorm @luxas are you guys still looking into this?

@luxas
Copy link

luxas commented Nov 24, 2019

I'm not, I've stepped down from kubeadm day-to-day development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants