-
Notifications
You must be signed in to change notification settings - Fork 615
Perform Implementations page review for v1.4 #4238
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
base: main
Are you sure you want to change the base?
Conversation
|
Skipping CI for Draft Pull Request. |
|
/hold for the three week right-of-reply period. |
robscott
left a comment
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.
Thanks @youngnick!
Content LGTM, I know we're not going to merge for another 3 weeks, but LGTM in advance of that.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: robscott, youngnick 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 |
This commit performs the Implemntations page review for Gateway API v1.4, using the process documented in the Implementations page. Signed-off-by: Nick Young <nick@isovalent.com>
Now that kubernetes-sigs#4233 merged. Signed-off-by: Nick Young <nick@isovalent.com>
6a1bb4f to
33e1c3a
Compare
What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
This commit performs the Implementations page review for Gateway API v1.4, using the process documented in the Implementations page.
Note that, as the Implementations page stands, we are not meeting the third-party links policy outlined in
kubernetes/enhancements#1327. There was further discussion around this in kubernetes/steering#292, which led to opening #3863 here some time ago.
The process allows for a minimum right-of-reply time of two weeks, but because it's Kubecon this week, I'm adding a week and making it three weeks instead.
So, implementations that wish to update their status can submit a conformance report sometime in the next three weeks (from the date of opening of this PR), and I will update the PR accordingly.
Otherwise, three weeks from today, this PR will be reviewed and merged as any normal PR, and these changes will become official.
This is the first time we've run this process, so I'm happy to accept feedback on it, although as I said above, any changes need to be satisfying the third-party links policy that covers the whole Kubernetes process.
Does this PR introduce a user-facing change?: