Add Backend Protocol Section to implementators guide

[dprotaso]

Comment: #2444 (comment)

[dprotaso]

/assign @youngnick - who's working on this now

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[youngnick]

Hmm, I had forgotten about this. The implementer's guide has now been, well, implemented, and is ready for someone to take the table that's currently in GEP-1911 (at https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols) and add a section that:

• explains that backend protocol selection exists
• links to the user guide (https://gateway-api.sigs.k8s.io/guides/backend-protocol/)
• includes the table from https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols with the expected support for backend protocol selection.

This is a reasonably straightforward documentation fix that is suitable for a new contributor.

/help
/good-first-issue
/remove-lifecycle stale

[k8s-ci-robot]

@youngnick:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Hmm, I had forgotten about this. The implementer's guide has now been, well, implemented, and is ready for someone to take the table that's currently in GEP-1911 (at https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols) and add a section that:

• explains that backend protocol selection exists
• links to the user guide (https://gateway-api.sigs.k8s.io/guides/backend-protocol/)
• includes the table from https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols with the expected support for backend protocol selection.

This is a reasonably straightforward documentation fix that is suitable for a new contributor.

/help
/good-first-issue
/remove-lifecycle stale

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.

[youngnick]

/unassign

[dprotaso]

/assign @dprotaso

[dprotaso]

/assign @joerober

[k8s-ci-robot]

@dprotaso: GitHub didn't allow me to assign the following users: joerober.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @joerober

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-sigs/prow repository.

[joerober]

/assign @joerober