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

Core API: NoMatchingParent RouteReason #481

Closed
kate-osborn opened this issue Mar 17, 2023 · 1 comment
Closed

Core API: NoMatchingParent RouteReason #481

kate-osborn opened this issue Mar 17, 2023 · 1 comment

Comments

@kate-osborn
Copy link
Contributor

kate-osborn commented Mar 17, 2023 •
edited by brianehlert
Loading

An HTTPRoute with a ParentRef that specifies a Port and/or SectionName that does not match any Listeners in the Gateway, should have Accepted/False/NoMatchingParent(Type/Status/Reason) Condition in its RouteParentStatus.

Acceptance Criteria:

  • The list of conditions in the RouteParentStatus should contain the condition Accepted/False/NoMatchingParent(Type/Status/Reason).
  • The RouteParentStatus should identify the ParentRef that caused the issue.
  • The RouteParentStatus should include a message that describes the problem. For example, specify if the port and/or the sectionName don't match.

Aha! Link: https://nginx.aha.io/features/NKG-65
@kate-osborn
Copy link
Contributor Author

duplicate of #306

@kate-osborn kate-osborn closed this as not planned Won't fix, can't repro, duplicate, stale Mar 17, 2023
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in NGINX Gateway Fabric Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
NGINX Gateway Fabric
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kate-osborn