Repository navigation
GEP-1619: Sync GEP with API Updates - #4870
Conversation
20f42ad to
dc8addd
Compare
Sync the GEP doc with current API state and clean up for readability: - Add graduation criteria checklist for Standard promotion - Replace implementations table with compact prior art table - Update failure behavior section to cover draining - Add note grandfathering of experimental status
|
@youngnick could I a quick look and approve? this should should be pretty non-controversial - mostly just an GEP sync with the latest API changes. |
|
/lgtm |
|
Thanks @kflynn - I have two maintainer LGTMs |
|
Oh I guess you can't approve @kflynn @mikemorris can you provide the final approval? |
|
I'm pretty sure only @rikatz @youngnick and @robscott (and the SIG-Network leads) have approval powers per https://github.com/kubernetes-sigs/gateway-api/blob/main/OWNERS#L4-L6 and https://github.com/kubernetes-sigs/gateway-api/blob/main/OWNERS_ALIASES#L12-L15 /approve |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gcs278, kflynn, mikemorris The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@youngnick could I get you to approve this please? |
|
assigning for the approval |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gcs278, kflynn, mikemorris, youngnick The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Housekeeping PR to get the GEP in better shape before the next round of API changes. No major changes to the API or spec behavior.
Which issue(s) this PR fixes:
Fixes N/A
Does this PR introduce a user-facing change?: