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

ContainerSecurityContext not correctly applied. #553

Closed
yesoos opened this issue Feb 23, 2024 · 1 comment
Closed

ContainerSecurityContext not correctly applied. #553

yesoos opened this issue Feb 23, 2024 · 1 comment

Comments

@yesoos
Copy link

yesoos commented Feb 23, 2024

What steps did you take and what happened:
I wanted to set ContainerSecurityContext as in example in valuse.yaml:

ContainerSecurityContext:
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
    add: []
  readOnlyRootFilesystem: true

What did you expect to happen:
SecurityContext properly set on velero container.

The output of the following commands will help us better understand what's going on:
When i dump the yaml of deployed container greping the securitycontext it's set like that (and that's on Pod level not container)

securityContext: {}

Anything else you would like to add:
Also tried applying securityContext directly to the container and it does not allow it somehow. SecurityContext works fine for other deployments

Environment:

terraform helm provider v2.12.1
helm chart version 5.4.1
kubernetes version 1.27.7
Azure AKS
Ubuntu 22.04

@yesoos
Copy link
Author

yesoos commented Feb 23, 2024

PEBKAC - somehow missed that first C should be lowercase.

@yesoos yesoos closed this as completed Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant