-
Notifications
You must be signed in to change notification settings - Fork 480
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
Promote ReferenceGrant to Beta #1455
Promote ReferenceGrant to Beta #1455
Conversation
Hi @nathancoleman. 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. |
Thanks for working on this @nathancoleman! I'm going to hold off on reviewing this since it's still in draft state, but leave another comment here when it's ready for review. /ok-to-test |
@robscott can you take a look when you get a moment? |
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 for the work on this @nathancoleman!
hack/invalid-examples/v1alpha2/referencegrant/missing-from.yaml
Outdated
Show resolved
Hide resolved
served: true | ||
storage: false |
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.
Calling this out to be sure it's noticed. This approach makes sense to me and matches what we did for other resources as they initially graduated to beta.
aab9f49
to
b4c792f
Compare
This follows the pattern established by Gateway, HTTPRoute, etc. Specifically, the ReferenceGrantList type is not an alias since it needs to be able to specify the type of `Items` directly.
Others feel free to review. It seems that re-requesting a review from Rob removes all other reviewers |
@robscott to you for review when you get a moment |
Thanks @nathancoleman! This change LGTM, but I want to get another maintainer to sign off before merging since this represents graduating a resource to beta. /approve |
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.
Looks like we need to update GEP-709 and mark it as standard
as well
@shaneutt what change are you looking for there? I don't see anything in the GEP template or other GEPs that looks related |
You'll wanna update the GEP status here to gateway-api/site-src/geps/gep-709.md Line 4 in 2f7ab68
And move it under "Standard" here: Line 86 in 2f7ab68
Also I would recommend taking one quick pass over the GEP just to make sure everything in it is accurate to the current API state, and if not update it to be in sync. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nathancoleman, robscott, 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 feature
/kind api-change
What this PR does / why we need it:
Graduates the
ReferenceGrant
resource tov1beta1
and thestable
release channelWhich issue(s) this PR fixes:
Fixes #1448
Does this PR introduce a user-facing change?: