[NET-6464] lock down init container #3959
Merged
Conversation
This file contains 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
sarahalsmiller
added
pr/no-changelog
|
LGTM, but similar here I think we should probably have a changelog entry for this |
sarahalsmiller
force-pushed
the
NET-6464-Lock-down-security-context-for-API-gateway-connect-inject-init-container
branch
2 times, most recently
from
a9a1165
to
c09b53b
Compare
sarahalsmiller
removed
the
pr/no-changelog
sarahalsmiller
force-pushed
the
NET-6464-Lock-down-security-context-for-API-gateway-connect-inject-init-container
branch
from
c09b53b
to
830917a
Compare
…gateway-connect-inject-init-container
jm96441n
approved these changes
Jun 4, 2024
nathancoleman
changed the title
sarahalsmiller
deleted the
NET-6464-Lock-down-security-context-for-API-gateway-connect-inject-init-container
branch
This was referenced Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes proposed in this PR
How I've tested this PR
How I expect reviewers to test this PR
Checklist