-
Notifications
You must be signed in to change notification settings - Fork 621
[GEP-1651]: Updated Types & Move to Experimental #2157
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
Conversation
This allows the status type to evolve separately from the spec type
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 @dprotaso!
|
/hold need to add the inline validation and drop the godoc linking |
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 @dprotaso!
| from a reserved pool. \n Implementations that support GatewayRoutability | ||
| MUST include an address that has the same routable semantics as | ||
| defined in the Gateway spec. \n Implementations MAY add additional | ||
| addresses in status, but they MUST be semantically less than the | ||
| scope of the requested scope. For example if a user requests a `Private` | ||
| routable Gateway then an additional address MAY have a routability | ||
| of `Cluster` but MUST NOT include `Private`." |
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.
Not a blocker for this PR, but unfortunate that we don't have a way to limit spec changes like this to experimental CRDs yet: #2160.
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.
Related: kubernetes-sigs/controller-tools#705
We could prune fields based on markers
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.
Though controller-tools folks don't want to maintain such a feature - so you could do some post-processing of the CRDs
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.
Yep, we are already doing some custom generation here (see #2160) we just need to extend it further to support this use case.
|
Thanks @dprotaso! Will leave hold in place for someone else to review + approve, but LGTM. /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, robscott 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 |
|
FYI - you can configure prow to squash everything by default so you don't need to add a label |
|
/hold cancel |
This expects the following to be merged first: #2144
See just the commit for just this PR - f9d4bbf
What type of PR is this?
/kind gep
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of #1651
Does this PR introduce a user-facing change?: