-
Notifications
You must be signed in to change notification settings - Fork 488
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.
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
improve SectionName examples and documentation for well-known resources #2946
improve SectionName examples and documentation for well-known resources #2946
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
/approve
/cc @robscott
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikemorris, shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks @mikemorris! /lgtm |
/retest |
/retest |
/lgtm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Addresses concerns from #2813 (comment) that the behavior of
SectionName
for well-known resources is not sufficiently documented.* HTTPRoute: HTTPRouteRule name
to this as a followup if Adding GEP-995 for support for named route rules #2593 merges first @guicassolatoWhich issue(s) this PR fixes:
Refs #1031 , #2593
Does this PR introduce a user-facing change?:
/cc @candita