-
Notifications
You must be signed in to change notification settings - Fork 472
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
add github workflow to check supportedFeatures freshness #2754
add github workflow to check supportedFeatures freshness #2754
Conversation
569a4ca
to
7d365b9
Compare
7d365b9
to
916d8c4
Compare
c4b5850
to
b40893e
Compare
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.
I like the idea of this change, it's definitely going to remove the issue of the validation getting out of sync. I just have a small suggestion
b6b6dab
to
54fd807
Compare
50b0f16
to
ba96bfe
Compare
Thanks @LiorLieberman! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LiorLieberman, 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 |
What type of PR is this?
/kind test
/area conformance
What this PR does / why we need it:
Kubebuilder validation gets out of date is someone is adding a supportedFeature.
When a gateway controller publish supportedFeatures into the GWC, the validation blocks it if some features are not in that list.
Right now, suite.AllFeatures contains features that are not in the validation.
Which issue(s) this PR fixes:
This enables the implementation of #2163 in gateway controllers by fixing the discrepancy between the validation list and the actual features.
It also keep freshness of this kubebuilder validation list
Does this PR introduce a user-facing change?: