-
Notifications
You must be signed in to change notification settings - Fork 472
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
Add implementations documentation #565
Add implementations documentation #565
Conversation
Welcome @shaneutt! |
Hi @shaneutt. 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 Once the patch is verified, the new status will be reflected by the 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. |
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.
When I first made this doc it felt sort of odd to do write ups for other projects (I represent Kong), but I tried to pull information from previous conversations in SIG networking zoom syncs and the K8s slack channel.
@robscott I would appreciate your review on this prior to moving it out of draft phase, perhaps I should stick with yours and mine implementations only for now? Not really sure since I'm new to the project, let me know 🖖
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.
See comments :)
In https://github.com/kubernetes-sigs/gateway-api/pull/565/files#r583944465 we discussed removing the version support table for now. Perhaps later we'll come back to it when there are more released and stable versions of Gateway API.
We'll need to add more context about the relationship between the Gateway API and Knative as part of some future iteration.
At this point I think we've received enough maintainer feedback and updated for that feedback that this PR is ready to move from draft to ready. Please let me know any other considerations, or changes that you feel need to be made! 🖖 |
/ok-to-test |
Let's see if we can get an approval from maintainers from each implementation: Contour: @stevesloka |
|
||
## Implementation Status | ||
|
||
- [Contour][1] (alpha) |
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.
can we make this a table?
| Implementation | Status |
| ---- | ---- |
etc
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.
Also, if we can put the version implemented (instead of just Alpha)
that would be useful for users
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.
e.g. Supports v1alpha1
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.
When this was in draft it started out as a table, see:
However @robscott had particularly requested that I change it to the format you see here.
If Rob is OK with changing it back to a table but using the format you suggest above, that sounds good to me. Just want to check with him.
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.
This is a minor thing and we can change in a later diff. My thinking was that table is easier to deal with more info (say which versions are supported)
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.
I also think a table would be a bit cleaner (though we don't have to block this PR). The original table had the vendors as columns instead of rows which doesn't leave much room for written content. The following format would allow us to take the existing written content we have in the page and surface it through a table.
| Implementation | Status |
| [Project/Product](link) | Explanation of progress towards support and/or support levels (which versions) |
| [Project/Product](link) | Explanation of progress towards support and/or support levels (which versions) |
etc
I think support is a gray area right now since we are early in the spec so it's prob too early for a clean cut version/checkmark box.
/hold |
I put a hold -- let's collect ack from the impls This looks great |
Just following up on Harry's summary from above, looks like we have most approvals, but still need a couple more. We currently have approvals for:
We still need approval from:
/assign @stevesloka @SantoDE |
@robscott: GitHub didn't allow me to assign the following users: stevesloka, SantoDE. Note that only kubernetes-sigs members, 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. 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. |
|
||
Traefik currently supports the previous `v0.1.x` Gateway API specification, check the [Kubernetes Gateway Documentation][traefik-1] for information on how to deploy and use Traefik's Gateway implementation. | ||
|
||
Traefik is currently working on implementing TCP, status updates and documentation will be provided here as the work progresses. |
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.
Traefik is currently working on implementing TCP, status updates and documentation will be provided here as the work progresses. | |
Traefik is currently working towards updating the integration to the current version `v0.2.x`, TCP as well as more status updates and documentation will be provided here as the work progresses. |
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.
Just one nitpick :)
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.
One minor edit outstanding, apart from that im LGTM
|
||
Traefik currently supports the previous `v0.1.x` Gateway API specification, check the [Kubernetes Gateway Documentation][traefik-1] for information on how to deploy and use Traefik's Gateway implementation. | ||
|
||
Traefik is currently working on implementing TCP, status updates and documentation will be provided here as the work progresses. |
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.
Just one nitpick :)
LGTM for the Contour bits! 🎉 |
## Implementation Status | ||
|
||
- [Contour][1] (alpha) | ||
- [Google Cloud][2] (work in progress) |
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.
Should be:
- [Google Kubernetes Engine][2] (work in progress)
I'm going to merge this and have the remaining comments addressed as follow up PRs. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, howardjohn, SantoDE, 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 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
As per [k8s slack conversations][slack] and #558 this PR adds documentation to keep track of the downstream Gateway API implementations in other projects.
Which issue(s) this PR fixes:
Fixes #558
Does this PR introduce a user-facing change?:
NONE