-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
genericapiserver: more dependency cutoffs #40216
Conversation
|
@@ -30,15 +30,15 @@ import ( | |||
"k8s.io/apiserver/pkg/authentication/request/x509" | |||
"k8s.io/apiserver/pkg/authentication/token/tokenfile" | |||
"k8s.io/apiserver/pkg/authentication/user" | |||
"k8s.io/apiserver/plugin/pkg/authenticator/password/keystone" |
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 wasn't expecting all these to move. We have an apiserver dependency or is it just kubeapiserver?
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.
keystone is simple, no deps left
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.
authorizers have more dependencies. Only moved webhook there.
_ "k8s.io/client-go/pkg/apis/authentication/install" | ||
_ "k8s.io/kubernetes/pkg/apis/authentication/install" |
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.
good change
|
@deads2k yes, they are optional, but independent enough to not harm, if you really build your kube-independent apiserver. |
General comment on the authentication packages. I think of plugins as optional and I don't think the webhook is optional and these are registering themselves for activation like normal plugins, so I'm not sure calling them plugins is appropriate. Certainly not blocking, but of note. |
Right about "plugin". Didn't want to change that here. Maybe for a follow-up. |
|
|
|
@@ -2034,7 +2035,7 @@ func ValidateAppArmorPodAnnotations(annotations map[string]string, spec *api.Pod | |||
if !strings.HasPrefix(k, apparmor.ContainerAnnotationKeyPrefix) { | |||
continue | |||
} | |||
if !utilflag.DefaultFeatureGate.AppArmor() { | |||
if !utilfeature.DefaultFeatureGate.Enabled(features.AppArmor) { |
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.
This is really ugly and generally wrong. Not new in this pull but the link here should be snipped. This is an admission choice, not a general validation choice.
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.
Will add a TODO. Didn't look at the meaning of the gates.
|
949e31f
to
e588602
Compare
7cb44ae
to
7095be0
Compare
561f6bc
to
f540fbf
Compare
Jenkins Bazel Build failed for commit f540fbfd8420a2dc0607ae24465c48eea1af4c1b. Full PR test history. The magic incantation to run this job again is 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. |
@k8s-bot cri node e2e test this |
@k8s-bot bazel test this |
Jenkins GCI GKE smoke e2e failed for commit f540fbfd8420a2dc0607ae24465c48eea1af4c1b. Full PR test history. The magic incantation to run this job again is 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. |
Jenkins verification failed for commit f540fbfd8420a2dc0607ae24465c48eea1af4c1b. Full PR test history. The magic incantation to run this job again is 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. |
@sttts keep your pull away from mine, just in case it contagious! :) |
Looking forward to yet another rebase tomorrow morning. Trying to understand the flake, maybe this:
@eparis ^^ |
f540fbf
to
2b8e938
Compare
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 39260, 40216, 40213, 40325, 40333) |
pkg/cert -> k8s.io/apimachinery (will rebase on @deads2k's PR also moving it)