Skip to content

Add missing word in Introduction #971

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

Merged
merged 1 commit into from
Dec 21, 2021
Merged

Add missing word in Introduction #971

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
4 changes: 2 additions & 2 deletions site-src/v1alpha2/references/cross-namespace-references.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ in a another namespace, or possibly Secrets may be referred to by Gateways or
Routes in another namespace.

In the past, we've seen that forwarding traffic across namespace boundaries is a
desired feature, but a safeguard like ReferencePolicy,
desired feature, but without a safeguard like ReferencePolicy,
[vulnerabilities](https://github.com/kubernetes/kubernetes/issues/103675) can emerge.

!!! note
Expand Down Expand Up @@ -124,4 +124,4 @@ above.

Other "ImplementationSpecific" objects and references MUST also use this flow
for cross-namespace references, except as noted in the Exceptions section
above.
above.