feat: refactor redis-ha NetworkPolicy to include egress rules (#9968) #10226
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.
Fixes #9968
This policy change includes egress rules to only allow DNS traffic outbound and maintain inter-Redis and Sentinel connectivity.
argocd-redis-ha-server & argocd-redis-ha-proxy
should not be allowed to communicate with other pods in the cluster to prevent lateral movement in the event a redis pod is breached.Signed-off-by: Justin Marquis 34fathombelow@protonmail.com
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: