Docs: clarify SectionName

[sdarwin]

Hi,

On this page of documentation, the setting "SectionName" is explained. While it mentions the effect of adding a "SectionName" it may be slightly lacking in clarifying the default which would be the absence of a "SectionName". What happens without it?

My assumption, and what's added in this pull request, is that it will "attach to all listeners" of that gateway.

As evidence about the importance of addressing the topic, it seems that even Google's documentation has gotten confused?
Consider on this page

https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-gateways

"""
When configuring HTTP-to-HTTPS redirects on the Gateway, the sectionName field is optional. If you don't configure this field, the HTTPS listener is automatically selected as the default option.
"""

What they have just said is "If you don't configure this field (sectionName), a particular listener (the HTTPS listener) is selected." I believe that's wrong and the fact is "If you don't configure this field (sectionName), all listeners are selected." In either case, it can't hurt to be sure this api-overview page has an answer.

/kind documentation

[k8s-ci-robot]

Welcome @sdarwin!

It looks like this is your first PR to kubernetes-sigs/gateway-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/gateway-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @sdarwin. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[keithmattix]

I think this is a clarity improvement

[keithmattix]

/ok-to-test

[robscott]

Thanks @sdarwin!

/release-note-none
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: keithmattix, robscott, sdarwin

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:

• site-src/OWNERS [robscott]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment