Skip to content
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

pod frequent create and delete by daemonset controller when kube-apiserver enabled PodNodeSelector admission controll #60960

Closed
lidajia opened this issue Mar 9, 2018 · 3 comments
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@lidajia
Copy link

lidajia commented Mar 9, 2018

/kind bug

Pod frequent create and delete by daemonset controller when kube-apiserver enabled PodNodeSelector admission controll. When the daemonset's nodeSelector not cover the nodeSelector configured in PodNodeSelector adminssion controll, the schedule of daemonset pods will conflict with the PodNodeSelector adminssion controll. Is daemonset controller should cover this case?

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 9, 2018
@lidajia
Copy link
Author

lidajia commented Mar 9, 2018

/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 9, 2018
@aveshagarwal
Copy link
Member

This has been discussed before, and here is my comment: #51788 (comment) .

Please close this issue.

@aveshagarwal
Copy link
Member

Also annotate your DS's namespace by setting scheduler.alpha.kubernetes.io/node-selector:"".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Development

No branches or pull requests

3 participants