-
Notifications
You must be signed in to change notification settings - Fork 512
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
GatewayClassObservedGenerationBump
feature type
#1780
Comments
This relates back to #1584 which initiated the change in the first place. In retrospect I believe the intention was to make this part of core conformance, as every implementation should be updating object status to indicate (for each condition) that they've seen the latest generation of the object. |
/help |
/assign |
/remove-help |
Blocked on #1822 |
Just a status update that we're still blocked on #1822, once that is complete we should probably add this to the agenda for a few meetings in a row to give people a heads up of our intention to make it core and then go for it at some point prior to GA. |
What happened:
GatewayClassObservedGenerationBump
is marked as an additional feature, but it Is marked neither as extended conformance nor as experimental conformance:gateway-api/conformance/utils/suite/suite.go
Lines 56 to 57 in f6d4eb7
My guess is that it is extended conformance, is it correct? If so, we should add
(extended conformance)
at the end of the comment line as all the other features above and below.The text was updated successfully, but these errors were encountered: