-
Notifications
You must be signed in to change notification settings - Fork 468
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
docs: specify the route kinds compatible with each protocolType #1515
Comments
/kind docs |
@mlavacca: The label(s) In response to this:
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. |
/kind documentation |
I would like to take this @shaneutt |
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 A similar disclaimer applies to |
@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 |
@ashutosh887 how are things going? Need any help moving this forward? |
Still want this, but we expect it will be OK to have this after |
I'm working on this. Haven't got the time to respond yet. Will do soon |
@mlavacca this is the table that I intend to make changes upon: 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 |
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:
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
/reopen |
@mlavacca: Reopened this issue. In response to this:
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. |
/remove-lifecycle rotten |
Reopening as #2263 has been reverted /reopen |
@mlavacca: Reopened this issue. In response to this:
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. |
What would you like to be added:
The listener spec field
allowedRoutes.kinds
documentation states: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.
The text was updated successfully, but these errors were encountered: