Skip to content

Commit 7db740b

Browse files
committed
docs(gateway-api): correct attachedNamespaces config path
Layer 1 of the Security section called the whitelist publishing.gateway.attachedNamespaces. The actual platform values schema (packages/core/platform/values.yaml on chore/gateway-api-crds-v1.5.1) puts attachedNamespaces directly under the root gateway: key, and the helm consumer (packages/core/platform/templates/apps.yaml) reads .Values.gateway.attachedNamespaces. The publishing.gateway path appears in the upstream PR description, the extra/gateway README, and one helm-fail string, but it is not the real config path. Use gateway.attachedNamespaces here to match the schema authors will actually configure. Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 927ca5f commit 7db740b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎content/en/docs/next/networking/gateway-api.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ flowchart TD
182182

183183
Every listener on a tenant Gateway pins `allowedRoutes.namespaces.from: Selector` to a `matchExpressions` whitelist against the built-in `kubernetes.io/metadata.name` label. That label is written by kube-apiserver on every namespace and cannot be spoofed.
184184

185-
The whitelist is the publishing tenant's namespace (always, implicit) plus `publishing.gateway.attachedNamespaces`. A namespace outside the list literally cannot attach any `HTTPRoute` or `TLSRoute` to the Gateway.
185+
The whitelist is the publishing tenant's namespace (always, implicit) plus `gateway.attachedNamespaces` from the platform Package. A namespace outside the list literally cannot attach any `HTTPRoute` or `TLSRoute` to the Gateway.
186186

187187
### Layer 2 — `cozystack-gateway-hostname-policy`
188188

0 commit comments

Comments
 (0)