-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Disable rbac/v1alpha1, settings/v1alpha1, and scheduling/v1alpha1 by default #51839
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Hi @jennybuckley. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/cc @caesarxuchao |
test/e2e/servicecatalog/podpreset.go
Outdated
@@ -22,7 +22,7 @@ import ( | |||
"time" | |||
|
|||
"k8s.io/api/core/v1" | |||
settings "k8s.io/api/settings/v1alpha1" | |||
settings "pkg/apis/settings" |
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.
Why is the import path changed?
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.
In this PR, we'll need to make this test a feature test, by adding [Feature:PodPreset]
in the test name, then the test won't run in pull-kubernetes-e2e-gce-etcd3.
In another PR, we need to add the test to the alpha suite, https://github.com/kubernetes/test-infra/blob/52b103fadb98e290d67fefeba6051eea8110fc46/jobs/config.json#L639.
cc @droot
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.
@caesarxuchao I think I have fixed the issue now, when you have time, could you look it over again?
Thanks
@jennybuckley with this change would enabling RBAC require feature flags for e.g. in 1.8 ? |
cc @roycaihw |
Created kubernetes/test-infra#4392 to add the podpreset tests to the alpha suite |
@krmayankk yes, but only rbac/v1alpha1 will need that as rbac/v1beta1 and rbac/v1 are still enabled by default |
@caesarxuchao squashed |
this just affects surfaced APIs, right, not the ability to decode in etcd? /ok-to-test |
pkg/master/master.go
Outdated
// See https://github.com/kubernetes/kubernetes/pull/47690. | ||
// TODO: disable rbac/v1alpha1 and settings/v1alpha1 by default in 1.8 | ||
rbacv1alpha1.SchemeGroupVersion, | ||
settingv1alpha1.SchemeGroupVersion, | ||
schedulingapiv1alpha1.SchemeGroupVersion, |
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.
Eh, the schduelingv1alpha1 is enabled by default. It's introduced in 1.8, so we can just remove it from the list. @jennybuckley could you remove this line as well?
cc @bsalamat the original author.
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.
Yes, I removed it as well as from the build file and the imports.
I was going to bring it up because I noticed that there was another alpha feature enabled by default, but I wasn't sure if that was intentional.
/assign @sttts |
tagging owning sigs - @kubernetes/sig-auth-api-reviews @kubernetes/sig-scheduling-api-reviews @kubernetes/sig-apps-api-reviews lgtm for sig-apps We do not enable alpha APIs by default. rbac and podpresents were accidentally enabled by default in previous releases. We announced in 1.7 they would be disabled by default in 1.8 (and how to re-enable with --runtime-config). This should merge to complete that work and ensure we do not enable a new alpha API by default in 1.8 |
a test like liggitt@746a119 would prevent alpha versions from getting re-added accidentally |
/retest |
lgtm for disabling alpha scheduling APIs by default. It was not my intention to enable them by default. |
@jennybuckley @bsalamat : looks like this is stuck on a new test to be written. right? |
Can just pick liggitt@746a119 if you like |
@liggitt should I add this test to this PR, or in a separate one? |
I can open separately |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jennybuckley, liggitt, sttts Associated issue: 47691 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 51839, 51987) |
What this PR does / why we need it: Disables alpha features which were previously enabled by default. Also changes tests which relied on these alpha features being enabled by default.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #47691Special notes for your reviewer:
Release note: