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

Pod Security Admission warnings #192

Open
mrclrchtr opened this issue Apr 4, 2024 · 0 comments · May be fixed by #210
Open

Pod Security Admission warnings #192

mrclrchtr opened this issue Apr 4, 2024 · 0 comments · May be fixed by #210
Labels
bug Something isn't working

Comments

@mrclrchtr
Copy link

When I deploy connect with helm, I get the following warnings with Pod Security Admission enabled:

Warning: would violate PodSecurity "restricted:latest": unrestricted capabilities (containers "connect-api", "connect-sync" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or containers "connect-api", "connect-sync" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers "connect-api", "connect-sync" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "curl" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "curl" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "curl" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "curl" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

It would be very good to fix these security warnings.

@mrclrchtr mrclrchtr added the bug Something isn't working label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant