Tbt/auth daemon config secret#1333
Open
TBThomas56 wants to merge 4 commits into
Open
Conversation
TBThomas56
force-pushed
the
tbt/auth-daemon-config-secret
branch
from
a87080a to
1125443
Compare
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.
Distributes auth-daemon-config secret to session namespaces from workflows namespace (GeneratingPolicy) and enforces access controls to protect sensitive content
Cronjob acts as fallback for existing namespaces and secret rotation.
Kyverno clusterpolicy enforces that only containers running the auth-daemon image may mount or reference the secret and blocks any exec into any pod that runs auth-daemon.
PS: I believe pods running alongside it can access it