-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Enable ClusterResourceSet by default #4213
🌱 Enable ClusterResourceSet by default #4213
Conversation
Kubernetes features are enabled by default when the features become beta. |
This is true, we can switch it to a beta experiment. I think we've had enough soak time so far.
Following upstream Kubernetes feature gate model, like Sedef mentioned, there are a bunch of features that are enabled as part of an experiment that are either alpha or beta. Or are we saying that we want only alpha features in exp/? |
following the k8s model and moving it to beta in exp SGTM |
+1 to graduate CRS to beta cluster-api/config/manager/manager.yaml Line 25 in 280db9a
And documentation about experimental features Might be there is also some other place like e.g. tests config files... |
Signed-off-by: Vince Prignano <[email protected]>
fb07101
to
2db2e49
Compare
This is ready to go |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
Signed-off-by: Vince Prignano [email protected]
What this PR does / why we need it:
Graduate CRS in v0.4.0 by enabling the functionality by default.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #3311
/milestone v0.4.0
/assign @CecileRobertMichon @sedefsavas