-
Notifications
You must be signed in to change notification settings - Fork 538
GEP-1713 Revisions #3744
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?
GEP-1713 Revisions #3744
Conversation
- Route attachment without sectionName - re-order policy attachment section - include a section about ReferenceGrants
daaa5f1
to
c1eac08
Compare
cc @howardjohn |
We had to drop the use of the PortNumber type because of limitations with overriding min max using kubebuilder annotations
Couple of small wording things, but aside from that, the GEP changes look good to me. The point about non-distinct |
Co-authored-by: Nick Young <[email protected]>
64832c3
to
b1e12f7
Compare
b1e12f7
to
8d6183c
Compare
I pulled the Port API changes into a separate PR - #3750 |
bump |
This LGTM now, so I'll approve. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, 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 |
@youngnick who should drop the hold? |
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!
// a unique port. If the implementation does not support dynamic port | ||
// assignment, it MUST set `Accepted` condition to `False` with the | ||
// `UnsupportedPort` reason. | ||
// | ||
// Support: Core | ||
// | ||
// +optional | ||
Port *PortNumber `json:"port,omitempty"` | ||
// | ||
// +kubebuilder:validation:Minimum=0 |
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.
Do you mind leaving this change out until we have docs for ListenerSet? At this point these are the only docs we have for ListenerSet, so I'd rather this match what's been released in the API until we can add those. (
Port PortNumber `json:"port"` |
#### Port | ||
|
||
`Port` is now optional to allow for dynamic port assignment. If the port is unspecified or set to zero, the implementation will assign a unique port. If the implementation does not support dynamic port assignment, it MUST set `Accepted` condition to `False` with the `UnsupportedPort` reason. |
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.
Same comment as above - would rather leave this out until we have docs that match current state
What type of PR is this?
/kind cleanup
/kind gep
What this PR does / why we need it:
As folks are implementing ListenerSets some clarifying questions came up and I thought it'd be good to revise the GEP with the answers.
Which issue(s) this PR fixes:
Fixes N/A
Does this PR introduce a user-facing change?: