Skip to content
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

Jump to bottom

Gateway API: use "RefNotPermitted" condition reason for invalid cross-namespace refs #4479

Closed
skriss opened this issue Apr 18, 2022 · 0 comments · Fixed by #4482
Closed

Gateway API: use "RefNotPermitted" condition reason for invalid cross-namespace refs #4479

skriss opened this issue Apr 18, 2022 · 0 comments · Fixed by #4482
Assignees
@skriss
Labels
area/gateway-api Issues or PRs related to the Gateway (Gateway API working group) API. kind/bug Categorizes issue or PR as related to a bug.

Comments

@skriss
Copy link
Member

skriss commented Apr 18, 2022

No description provided.

@skriss skriss added kind/bug Categorizes issue or PR as related to a bug. area/gateway-api Issues or PRs related to the Gateway (Gateway API working group) API. labels Apr 18, 2022
@skriss skriss self-assigned this Apr 18, 2022
skriss added a commit to skriss/contour that referenced this issue Apr 18, 2022
@skriss
internal/dag: use RefNotPermitted reason when applicable
effc056 
When an HTTPRoute or TLSRoute has a cross-namespace
backend ref that's not permitted by a ReferencePolicy,
use the RefNotPermitted condition reason.

Closes projectcontour#4479.

Signed-off-by: Steve Kriss <krisss@vmware.com>
@skriss skriss mentioned this issue Apr 18, 2022
Merged
skriss added a commit to skriss/contour that referenced this issue Apr 18, 2022
@skriss
internal/dag: use RefNotPermitted reason when applicable
56fb653 
When an HTTPRoute or TLSRoute has a cross-namespace
backend ref that's not permitted by a ReferencePolicy,
use the RefNotPermitted condition reason.

Closes projectcontour#4479.

Signed-off-by: Steve Kriss <krisss@vmware.com>
skriss added a commit that referenced this issue Apr 18, 2022
@skriss
internal/dag: use RefNotPermitted reason when applicable (#4482)
325b777 
When an HTTPRoute or TLSRoute has a cross-namespace
backend ref that's not permitted by a ReferencePolicy,
use the RefNotPermitted condition reason.

Closes #4479.

Signed-off-by: Steve Kriss <krisss@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skriss skriss

Labels
area/gateway-api Issues or PRs related to the Gateway (Gateway API working group) API. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

internal/dag: use RefNotPermitted reason when applicable skriss/contour
1 participant
@skriss