-
Notifications
You must be signed in to change notification settings - Fork 4
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
Not possible to indicate "no taints" #63
Comments
Since provider users want master Nodes to have no taints in order to allow Pods to be scheduled on them, I propose that users use the |
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Jan 24, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Jan 24, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Jan 28, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Jan 29, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Feb 7, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Feb 8, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Feb 11, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Feb 22, 2019
Workaround for platform9/ssh-provider#63
dlipovetsky
pushed a commit
to platform9/cctl
that referenced
this issue
Feb 23, 2019
Workaround for platform9/ssh-provider#63
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to kubernetes-sigs/cluster-api#707 and kubernetes/kubeadm#1358, it is not possible to indicate that a node should have no taints.
The text was updated successfully, but these errors were encountered: