Replies: 1 comment
-
This should be basically what you want: https://buoyant.io/2021/12/14/locking-down-network-traffic-between-kubernetes-namespaces/ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have a cluster with ~10 namespaces, some are infrastructure based(external secrets), or mon(grafana,prometheus).
The same cluster contains team specific namespaces(team1, team2).
I am looking to create a fairly simple policy that leaves metrics scraping and general communication unchanged(scraping, web hooks, etc), while blocking any requests from team1's namespace to team2's namespace. Is there an example of this simple policy?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions