Skip to content

docs(gateway): fix default-deny step for namespaced mode #2802

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.

Sign up for GitHub

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

Draft
electricjesus wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs(gateway): fix default-deny step for namespaced mode #2802

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions calico-enterprise/networking/ingress-gateway/create-ingress-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,11 @@ You need to do the following:
## Create an ingress gateway

1. If you are using a [global default deny policy](../../network-policy/beginners/kubernetes-default-deny.mdx),
allow traffic through the gateway by adding the `tigera-gateway` namespace to the list of excluded namespaces in the
`namespaceSelector` field.
you do not need to allow the gateway proxy's own traffic. The Tigera Operator allows it through a
policy in the `calico-system` tier. You do need to allow the gateway proxy to reach your backend
workloads. The proxy pods carry the label `gateway.envoyproxy.io/owning-gateway-name`, so you can
select them in an egress rule. Without that rule, the gateway is reachable but returns `503` because
the proxy cannot connect to the backend.
Comment on lines +33 to +37

1. To enable Gateway API support, create a `GatewayAPI` resource with the name `tigera-secure`:

Expand Down
7 changes: 5 additions & 2 deletions calico/networking/ingress-gateway/create-ingress-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,11 @@ You need to do the following:
## Create an ingress gateway

1. If you are using a [global default deny policy](../../network-policy/get-started/kubernetes-default-deny.mdx),
allow traffic through the gateway by adding the `tigera-gateway` namespace to the list of excluded namespaces in the
`namespaceSelector` field.
you do not need to allow the gateway proxy's own traffic. The Tigera Operator allows it through a
policy in the `calico-system` tier. You do need to allow the gateway proxy to reach your backend
workloads. The proxy pods carry the label `gateway.envoyproxy.io/owning-gateway-name`, so you can
select them in an egress rule. Without that rule, the gateway is reachable but returns `503` because
the proxy cannot connect to the backend.
Comment on lines +33 to +37

1. To enable Gateway API support, create a `GatewayAPI` resource with the name `default`:

Expand Down