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

Add Pod securityContext for target allocator #2500

Conversation

husnialhamdani
Copy link
Member

Description:
Add Pod securityContext to target allocator as it was removed in previous changes.

Link to tracking Issue:
#2495

Testing:
Added a unit and E2E test to specifically check fields unique to the Pod security context.

@@ -0,0 +1,16 @@
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: breaking
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is an enhancement as you are adding fields here.

@@ -51,6 +51,7 @@ spec:
securityContext:
runAsUser: 1000
runAsGroup: 3000
fsGroup: 3000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i believe you need to set this in a different block for the podSecurityContext

Copy link
Member Author

@husnialhamdani husnialhamdani Jan 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@husnialhamdani husnialhamdani force-pushed the target-allocator-pod-security-context branch from cedd29b to 9ad50fb Compare January 10, 2024 16:58
@@ -56,6 +56,8 @@ spec:
operator: In
values:
- "true"
securityContext:
runAsUser: 1000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we assert the other properties here too?

      runAsGroup: 3000
      fsGroup: 2000

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

@husnialhamdani husnialhamdani marked this pull request as ready for review January 10, 2024 17:29
@husnialhamdani husnialhamdani requested a review from a team January 10, 2024 17:29
@jaronoff97 jaronoff97 requested a review from a team January 10, 2024 18:17
Copy link
Contributor

@swiatekm swiatekm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jaronoff97 jaronoff97 merged commit 2dde84f into open-telemetry:main Jan 11, 2024
27 checks passed
ItielOlenick pushed a commit to ItielOlenick/opentelemetry-operator that referenced this pull request May 1, 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

Successfully merging this pull request may close these issues.

3 participants