Skip to content
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

Merged

Conversation

shaneutt
Copy link
Member

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

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 26, 2021
@k8s-ci-robot
Copy link
Contributor

Welcome @shaneutt!

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
Copy link
Contributor

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 /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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 26, 2021
Copy link
Member Author

@shaneutt shaneutt left a 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 🖖

site-src/implementations.md Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
Copy link
Contributor

@SantoDE SantoDE left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments :)

site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
site-src/implementations.md Outdated Show resolved Hide resolved
shaneutt and others added 6 commits March 2, 2021 13:58
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.
@shaneutt shaneutt requested a review from robscott March 2, 2021 19:15
@shaneutt
Copy link
Member Author

shaneutt commented Mar 2, 2021

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! 🖖

@shaneutt shaneutt marked this pull request as ready for review March 2, 2021 19:16
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 2, 2021
@hbagdi
Copy link
Contributor

hbagdi commented Mar 4, 2021

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 4, 2021
@hbagdi
Copy link
Contributor

hbagdi commented Mar 4, 2021

Let's see if we can get an approval from maintainers from each implementation:

Contour: @stevesloka
GKE: @robscott @bowei
Istio: @howardjohn
Kong: Approved by mysefl and @shaneutt
Traefik: @SantoDE


## Implementation Status

- [Contour][1] (alpha)
Copy link
Contributor

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

Copy link
Contributor

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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

e.g. Supports v1alpha1

Copy link
Member Author

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:

#565 (comment)

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.

Copy link
Contributor

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)

Copy link
Contributor

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.

@bowei
Copy link
Contributor

bowei commented Mar 4, 2021

/hold
/approve

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 4, 2021
@bowei
Copy link
Contributor

bowei commented Mar 4, 2021

I put a hold -- let's collect ack from the impls

This looks great

@robscott
Copy link
Member

robscott commented Mar 9, 2021

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:

  • GKE
  • Istio
  • Kong

We still need approval from:

/assign @stevesloka @SantoDE

@k8s-ci-robot
Copy link
Contributor

@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.
For more information please see the contributor guide

In response to this:

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:

  • GKE
  • Istio
  • Kong

We still need approval from:

/assign @stevesloka @SantoDE

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one nitpick :)

Copy link
Contributor

@SantoDE SantoDE left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one nitpick :)

@stevesloka
Copy link
Contributor

LGTM for the Contour bits! 🎉

## Implementation Status

- [Contour][1] (alpha)
- [Google Cloud][2] (work in progress)
Copy link
Contributor

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)

@bowei
Copy link
Contributor

bowei commented Mar 10, 2021

I'm going to merge this and have the remaining comments addressed as follow up PRs.
/hold cancel
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 10, 2021
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 10, 2021
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 509d7d5 into kubernetes-sigs:master Mar 10, 2021
@shaneutt shaneutt deleted the shaneutt/implementations-docs branch March 10, 2021 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs Improvements
10 participants