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

Fix unconfigurable onegent classic privileged container #1254

Merged
merged 2 commits into from
Oct 18, 2022

Conversation

chrismuellner
Copy link
Collaborator

Description

classicFullStack does not require privileged container in call cases. By default it should use capabilities, only when the feature flag is set the container is privileged.

How can this be tested?

Deploy oneagent with the following configurations:

  • without privileged oneagent feature flag: oneagent security context should use capabiilties
  • with privileged oneagent feature flag: oneagent security context should be privileged

Checklist

  • Unit tests have been updated/added
  • PR is labeled accordingly
  • I have read and understood the contribution guidelines

@chrismuellner chrismuellner added the bug Something isn't working label Oct 18, 2022
@chrismuellner chrismuellner requested a review from a team as a code owner October 18, 2022 09:15
@chrismuellner chrismuellner enabled auto-merge (squash) October 18, 2022 10:33
@chrismuellner chrismuellner merged commit 9718141 into release-0.9 Oct 18, 2022
@chrismuellner chrismuellner deleted the fix/onegent-privileged branch October 18, 2022 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants