-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ingress: Update docs with network policy example #31060
Conversation
ec57b93
to
a1c5cab
Compare
/test |
Does it make sense to include a policy for the ingress itself too? Is that possible? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank you! I left a couple of wording and typo suggestions for you.
a1c5cab
to
7b1581d
Compare
I have added one more policy to allow ingress traffic from a specific cidr, let me know if it's what you have in mind. Thanks. |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two grammar nits, then LGTM! Thanks!
This is to extend the existing basic ingress docs with external lockdown CCNP, while still allows in-cluster traffic to Ingress LB IP. Relates: #28126 Signed-off-by: Tam Mach <tam.mach@cilium.io>
7b1581d
to
cff19ff
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for me
This is to extend the existing basic ingress docs with external lockdown CCNP, while still allows in-cluster traffic to Ingress LB IP.
Relates: #28126