Fixes calrissian #181 #186
Open
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
|
This also carries a few enhancements:
|
emmanuelmathot
approved these changes
Jan 24, 2025
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.
This PR adds command line interface options to set network access pod labels.
Then CWL CLT that specify the
NetworkAccessrequirement will run pods labelled according to the calrissian command-line values set.The implementation of the cluster network policies is of course out of the scope of calrissian. Without network policies, you only get labelled pods, nothing else :-)
These labels can thus be defined in NetworkPolicies to control the pod egress based on the CWL NetworkAccess requirement introduced in v1.1.