[Python]feat: Run auto-instrumentation init container as non-root user#736
Open
Miqueasher wants to merge 1 commit into
Open
[Python]feat: Run auto-instrumentation init container as non-root user#736Miqueasher wants to merge 1 commit into
Miqueasher wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Customers enforcing runAsNonRoot: true via Pod Security Standards cannot use ADOT auto-instrumentation. Kubernetes checks the image metadata for a USER directive, finds none (defaults to UID 0 / root), and rejects the pod with:
Error: container has runAsNonRoot and image will run as root
Summary
Enables customers using the Kubernetes Restricted Pod Security Standard to use ADOT auto-instrumentation
Without this change, customers enforcing runAsNonRoot: true at the namespace or pod level cannot use ADOT auto-instrumentation because Kubernetes rejects the init container with:
container has runAsNonRoot and image will run as root
Follows the upstream OTel Operator fix (open-telemetry/opentelemetry-operator#2272)
Changes
Add USER 65534:65534 to the auto-instrumentation Dockerfile so the init container runs as non-root by default
Testing
Validated on EKS cluster (us-east-1, EKS v1.34.6) with CW Observability add-on v5.3.1
For more in-depth analysis please see Test Results
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.