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.

Sign up for GitHub

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

Jump to bottom

Drop capabilities, enable seccomp and enforce runAsNonRoot #223

Merged
merged 1 commit into from
Jan 20, 2022
Merged

Drop capabilities, enable seccomp and enforce runAsNonRoot #223

merged 1 commit into from
Jan 20, 2022

Commits on Jan 20, 2022

  1. drop capabilities, enable seccomp and enforce runAsNonRoot 

    Further restricts the SecurityContext that the controller runs under, by enabling the default seccomp profile and dropping all linux capabilities.
This was set at container-level to ensure backwards compatibility with use cases in which sidecars are injected into the source-controller pod
without setting less restrictive settings.
Add a uid and gid for the container to enforce runAsNonRoot and ensure
the use of non root users.

BREAKING CHANGES:
1) The use of new seccomp API requires Kubernetes 1.19.
2) the controller container is now executed under 65534:65534 (userid:groupid).
   This change may break deployments that hard-coded the user name 'controller' in their PodSecurityPolicy.

Signed-off-by: Sanskar Jaiswal <jaiswalsanskar078@gmail.com>
Co-authored-by: Paulo Gomes <paulo.gomes@weave.works>
    @aryan9600
    aryan9600 and Paulo Gomes committed Jan 20, 2022
    Configuration menu
    Copy the full SHA
    d454180 View commit details
    Browse the repository at this point in the history