docs: specify the route kinds compatible with each protocolType

[mlavacca]

What would you like to be added:

The listener spec field allowedRoutes.kinds documentation states:

// Kinds specifies the groups and kinds of Routes that are allowed to bind
// to this Gateway Listener. When unspecified or empty, the kinds of Routes
// selected are determined using the Listener protocol.
//
// A RouteGroupKind MUST correspond to kinds of Routes that are compatible
// with the application protocol specified in the Listener's Protocol field.
// If an implementation does not support or recognize this resource type, it
// MUST set the "ResolvedRefs" condition to False for this Listener with the
// "InvalidRouteKinds" reason.

But there is no indication about the core kinds compatible with each protocolType. For this reason, an indication of which core routes are compatible for each protocol type is an important piece of information to add to the documentation.

Why this is needed:

This is needed to clearly state the core route kinds supported by each protocol type.

[mlavacca]

/kind docs

[k8s-ci-robot]

@mlavacca: The label(s) kind/docs cannot be applied, because the repository doesn't have them.

In response to this:

/kind docs

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.

[mlavacca]

/kind documentation

[ashutosh887]

I would like to take this @shaneutt

[youngnick]

I think this is fine, but it's important to specify that the ones included in Gateway API are examples, not a full list. It's also intended that if implementations add their own types of Routes, then they include those custom Routes in allowedRoutes.

A similar disclaimer applies to supportedKinds in the status stanza.

[shaneutt]

@ashutosh887 sounds good, but keep in mind this one could end up requiring some consensus building. Check in with us here or on K8s slack if you run into any questions along the way, and let us know how we can support you in this!

/assign @ashutosh887

[shaneutt]

@ashutosh887 how are things going? Need any help moving this forward?

[shaneutt]

Still want this, but we expect it will be OK to have this after v1.0.0. We can hold on it until after the release.

[abs007]

I'm working on this. Haven't got the time to respond yet. Will do soon

[mlavacca]

Thank you, @abs007!

/assign @abs007

[abs007]

@mlavacca this is the table that I intend to make changes upon:
https://docs.google.com/spreadsheets/d/1trCeFLYDCiTnpkhxCMaRQ8DuwxgafJmNQMCI5QgsmLk/edit?usp=sharing

I am currently trying to understand the kind supported for each protocol. Do you have any additional info that you could point me to? Thanks

[mlavacca]

@mlavacca this is the table that I intend to make changes upon: https://docs.google.com/spreadsheets/d/1trCeFLYDCiTnpkhxCMaRQ8DuwxgafJmNQMCI5QgsmLk/edit?usp=sharing

I am currently trying to understand the kind supported for each protocol. Do you have any additional info that you could point me to? Thanks

In addition to the list you provided here, I think we should add HTTPRoutes and GRPCRoutes to the HTTPS section. We should build consensus on this one. Therefore, I suggest you open a PR with such a table so that we can have a conversation there with the broader community.

[abs007]

Any specific location where I should place the table?

Also, I'll make it in markdown, I suppose?

[mlavacca]

Any specific location where I should place the table?

Also, I'll make it in markdown, I suppose?

I'd say we need such information in two different places:

1. in the documentation (md), in the form of a table. I'd say putting such a table in this file is ok.
2. in the code, in the form of comments.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.

[mlavacca]

/reopen

[k8s-ci-robot]

@mlavacca: Reopened this issue.

In response to this:

/reopen

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.

[mlavacca]

/remove-lifecycle rotten

[mlavacca]

Reopening as #2263 has been reverted

/reopen

[k8s-ci-robot]

@mlavacca: Reopened this issue.

In response to this:

Reopening as #2263 has been reverted

/reopen

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.