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

InitContainer lacks allowPrivilegeEscalation setting which triggers Azure Gatekeeper OPA #1084

Closed
ashpr opened this issue Sep 8, 2022 · 2 comments · Fixed by #1273
Closed
Labels
area:auto-instrumentation Issues for auto-instrumentation

Comments

@ashpr
Copy link

ashpr commented Sep 8, 2022

Hello,

I'm afraid to report that OpenTel instrumentation cannot be used with Azure Gatekeeper OPA because of Privilege Escalation not being explicitly set to False on the instrumentation initContainer securityContext.

image

Unless I'm mistaken I cant seem to find a way to explicitly override this. Would it be possible to set this (if privilege escalation is required) or allow it to be overridden via YAML Values?

@pavolloffay pavolloffay added the area:auto-instrumentation Issues for auto-instrumentation label Sep 12, 2022
@pavolloffay
Copy link
Member

@ashpr is this related to #1058 ? PRs are welcome to fix the issue.

@ashpr
Copy link
Author

ashpr commented Sep 12, 2022

@pavolloffay Good spot! Its definitely the same area although Azures OPA is a lot stricter and demands more, including runAsNonRoot being explicitly false.

I'm happy to give it a punt and test it against our cluster. Should this issue remain open or consolidate on #1058 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:auto-instrumentation Issues for auto-instrumentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants