-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Feature Gates for Federation APIs #38593
Comments
known issue for v1.5.0 #37134 |
I am going to take this up. I will need to enable them explicitly in tests that test those APIs. |
Sent #42225 to fix runtime-config support for federation-apiserver. We can now use the I am disabling batch and autoscaling groups in that PR since the controllers for those API resources havent merged yet. Am keeping all other APIs enabled by default. Am on the fence for deployments (since it has known issues in rollback) and ingress (only works on GCP). Would love to know what others think. This is related to the which resources are alpha vs beta discussion which we havent settled yet. |
Moving to 1.7 as late to happen in 1.6. Feel free to switch back if this is incorrect. |
Automatic merge from submit-queue (batch tested with PRs 44019, 42225) federation: Fixing runtime-config support for federation-apiserver Fixes #42587 Ref #38593 Fixing the broken `--runtime-config` flag support in federation-apiserver. Fixing the bugs and using it to disable batch and autoscaling groups. Users can enable them by passing `--runtime-config=apis/all=true` to federation-apiserver. ~This also includes a bug fix to kube-apiserver registry that allows users to disable api/v1 resources~ cc @kubernetes/sig-federation-pr-reviews
I realized this bug had 2 parts to it:
First part is done. Tracking second in #44291 |
Automatic merge from submit-queue (batch tested with PRs 44019, 42225) federation: Fixing runtime-config support for federation-apiserver Fixes kubernetes/kubernetes#42587 Ref kubernetes/kubernetes#38593 Fixing the broken `--runtime-config` flag support in federation-apiserver. Fixing the bugs and using it to disable batch and autoscaling groups. Users can enable them by passing `--runtime-config=apis/all=true` to federation-apiserver. ~This also includes a bug fix to kube-apiserver registry that allows users to disable api/v1 resources~ cc @kubernetes/sig-federation-pr-reviews
Federation control plane components don't support feature gates for non-GA APIs/features and must be implemented. See here for examples - https://github.com/kubernetes/kubernetes/blob/master/pkg/util/config/feature_gate.go.
cc @kubernetes/sig-federation @nikhiljindal
The text was updated successfully, but these errors were encountered: