Add a note to Ingress Gateway docs re global default deny#2727
Open
alexh-tigera wants to merge 2 commits into
Open
Add a note to Ingress Gateway docs re global default deny#2727alexh-tigera wants to merge 2 commits into
alexh-tigera wants to merge 2 commits into
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a warning to Ingress Gateway setup docs so users applying a global default deny policy exclude the tigera-gateway namespace.
Changes:
- Adds the same
:::noteto Calico, Calico Enterprise, and Calico Cloud Ingress Gateway creation docs. - Links the note to the product’s global default deny policy guidance.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
calico/networking/ingress-gateway/create-ingress-gateway.mdx |
Adds the default deny exclusion note for Calico OSS next docs. |
calico-enterprise/networking/ingress-gateway/create-ingress-gateway.mdx |
Adds the default deny exclusion note for Enterprise next docs. |
calico-cloud/networking/ingress-gateway/create-ingress-gateway.mdx |
Adds the default deny exclusion note for Cloud next docs. |
Comments suppressed due to low confidence (2)
calico-enterprise/networking/ingress-gateway/create-ingress-gateway.mdx:60
- This relative link is broken for the Enterprise docs:
calico-enterprise/network-policy/get-started/kubernetes-default-deny.mdxdoes not exist; the default deny page in this product is undernetwork-policy/beginners/kubernetes-default-deny.mdx. The current link will fail Docusaurus link validation and users cannot navigate to the referenced guidance.
If you are using a [global default deny policy](../../network-policy/get-started/kubernetes-default-deny.mdx), you must add the
calico-cloud/networking/ingress-gateway/create-ingress-gateway.mdx:60
- This relative link is broken for the Cloud docs:
calico-cloud/network-policy/get-started/kubernetes-default-deny.mdxdoes not exist; the default deny page in this product is undernetwork-policy/beginners/kubernetes-default-deny.mdx. The current link will fail Docusaurus link validation and users cannot navigate to the referenced guidance.
If you are using a [global default deny policy](../../network-policy/get-started/kubernetes-default-deny.mdx), you must add the
Comment on lines
+59
to
+62
| :::note | ||
| If you are using a [global default deny policy](../../network-policy/get-started/kubernetes-default-deny.mdx), you must add the | ||
| `tigera-gateway` namespace to the list of excluded namespaces in the `namespaceSelector` field. | ||
| ::: |
Collaborator
There was a problem hiding this comment.
Let's include this as part of the procedure.
Add your line as the final step:
- If you're using a global default deny policy, allow traffic through the gateway by adding the
tigera-gatewaynamespace to the list of excluded namespaces in thenamespaceSelectorfield.
Member
Author
There was a problem hiding this comment.
Ok, that makes sense. I think it should be the first step though - if you have a default deny, the envoy pods fail to deploy, and would go into a crash loop backoff until the traffic is allowed. Doing it first would allow it to start cleanly. WDYT?
alexh-tigera
force-pushed
the
alexh-ci-1950-add-note-for-ingress-gateway-with-default-deny
branch
2 times, most recently
from
7efbaa9 to
4cd47dc
Compare
ctauchen
reviewed
May 14, 2026
Collaborator
ctauchen
left a comment
ctauchen
left a comment
There was a problem hiding this comment.
I suggest we move this to part of the procedure. We hope that nearly everyone uses a default deny, so this should be necessary for most.
Comment on lines
+59
to
+62
| :::note | ||
| If you are using a [global default deny policy](../../network-policy/get-started/kubernetes-default-deny.mdx), you must add the | ||
| `tigera-gateway` namespace to the list of excluded namespaces in the `namespaceSelector` field. | ||
| ::: |
Collaborator
There was a problem hiding this comment.
Let's include this as part of the procedure.
Add your line as the final step:
- If you're using a global default deny policy, allow traffic through the gateway by adding the
tigera-gatewaynamespace to the list of excluded namespaces in thenamespaceSelectorfield.
Ingress Gateway fails to start when a default deny rule is applied to the tigera-gateway namespace. Add a note to the ingress gateway setup docs to exclude it from the deny rules.
alexh-tigera
force-pushed
the
alexh-ci-1950-add-note-for-ingress-gateway-with-default-deny
branch
from
4cd47dc to
95a603e
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
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.
Ingress Gateway fails to start when a default deny rule is applied to the tigera-gateway namespace. Add a note to the ingress gateway setup docs to exclude it from the deny rules.
Product Version(s):
Issue:
https://tigera.atlassian.net/browse/EV-6476
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: