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
charts: fix master and control-plane nodeSelectors #603
base: master
Are you sure you want to change the base?
Conversation
An empty value in a nodeSelector is not treated as a wildcard.
Welcome @intelfx! |
Hi @intelfx. Thanks for your PR. I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: intelfx The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
{{- end}} | ||
{{- if .Values.controller.runOnControlPlane}} | ||
node-role.kubernetes.io/control-plane: "" | ||
node-role.kubernetes.io/control-plane: "true" |
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.
not sure whether all master node are labeled with node-role.kubernetes.io/control-plane: ""
, but as I know, the azure capz cluster are labeled as node-role.kubernetes.io/control-plane: ""
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 think you could set set --nodeSelector=xxx
to make it work on your testing env if existing config does not work on your testing env.
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 can, but it's a footgun. Also, as I remember, at least GKE also has "true"
instead of ""
.
Would you be open to a patch that replaces these node selector with node affinities (which make it possible to declare an "Exists" relation instead of a strict match)?
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, check exists is better than strict match, thanks.
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What type of PR is this?
/kind bug
What this PR does / why we need it:
controller.runOnMaster
andcontroller.runOnControlPlane
are non-functional as written, since an empty value in a nodeSelector is not treated as a wildcard. Fix the nodeSelectors to match against"true"
, which is enough to successfully schedule the controller on a master/control-plane node in my testing.Does this PR introduce a user-facing change?: