Repository navigation
docs: Document VirtualServer routeSelector no-match warning (NIC) - #2375
Merged
JTorreG merged 1 commit intoOct 6, 2026
Merged
Conversation
NGINX Ingress Controller now sets a VirtualServer to State: Warning and emits a Warning event when a routeSelector matches no VirtualServerRoutes (nginx/kubernetes-ingress#10913). Add a Warning events section to the VirtualServer troubleshooting page that lists the causes, shows the event, and explains how to clear it. Link to it from the RouteSelector reference.
2 tasks done
✅ Deploy Preview will be available once build job completes!
|
ciarams87
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Documents nginx/kubernetes-ingress#10913 (fixes nginx/kubernetes-ingress#10899), which ships in the next F5 NGINX Ingress Controller release. The change isn't cherry-picked onto
release-5.6, so this PR targetsnic-release-next.With this change, a VirtualServer whose
routeSelectormatches no VirtualServerRoutes reportsState: Warningand gets aWarningevent with theAddedOrUpdatedWithWarningreason. Before, it stayedValidwith no event. Routes attached by name already reported a warning when their VirtualServerRoute was missing.The maintainers settled the open questions from #10899 before the source PR merged. The warning appears whenever the selector matches nothing: the VirtualServerRoute was deleted, its
ingressClassNamechanged, its labels were removed, or the selector never matched. The warning doesn't block the configuration. If you detach a path on purpose, remove the route from the VirtualServer as well.What changed:
content/nic/troubleshooting/troubleshoot-virtualserver.md: adds a Warning events section. It covers what the warning means, the four conditions that cause it, an examplekubectl describe vsevent, and how to clear it.content/nic/configuration/virtualserver-and-virtualserverroute-resources.md: adds a note to the RouteSelector reference that links to the new section.Notes for the reviewer:
mainand was written before the behavior was settled, so close it without merging. This PR also adds the "selector never matched" case and the option to remove a route you no longer need.routeSelectorcan change fromValidtoWarningafter an upgrade. Release notes and changelog entries are left to the maintainers.Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩