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

appArmorProfile is removed from SecurityContext #3036

Closed
jbmolle opened this issue Jun 12, 2024 · 1 comment · Fixed by #3061
Closed

appArmorProfile is removed from SecurityContext #3036

jbmolle opened this issue Jun 12, 2024 · 1 comment · Fixed by #3061
Labels
bug Something isn't working needs triage

Comments

@jbmolle
Copy link

jbmolle commented Jun 12, 2024

Component(s)

No response

What happened?

Description

When creating a Pod or a Deploy with appArmorProfile into securityContext field, the appArmorProfile is removed by the mutating webhook.
Check kubernetes/kubernetes#125069

Steps to Reproduce

  1. Create a pod with a Yaml file containing
securityContext:
  appArmorProfile:
    type: Unconfined

The security context is there with kubectl apply -f xxx.yaml -oyaml --dry-run=server
2)Install opentelemetry-operator
3) Run again kubectl apply -f xxx.yaml -oyaml --dry-run=server, the securityContext appArmorProfile is gone

Expected Result

appArmorProfile should be present in securityContext

Actual Result

appArmorProfile is not there

Kubernetes Version

1.30.2

Operator version

0.102.0

Collector version

0.102.0

Environment information

Environment

OS: Ubuntu 22.04 / Ubuntu 24.04

Log output

No response

Additional context

No response

@swiatekm
Copy link
Contributor

As I mentioned in #3037 (comment), this is blocked on #3041, which is blocked by bumping our required Go version to 1.22 (#2757).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
2 participants