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.

Sign up for GitHub

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

Jump to bottom

calico-kube-controllers Pods not tied to infra (or even master?) nodes #2243

Closed
NicolasT opened this issue Feb 13, 2020 · 0 comments · Fixed by #2824
Closed

calico-kube-controllers Pods not tied to infra (or even master?) nodes #2243

NicolasT opened this issue Feb 13, 2020 · 0 comments · Fixed by #2824

Comments

@NicolasT
Copy link
Contributor

It appears that the calico-kube-controllers Pod(s) can be scheduled on any node. I believe these should only be scheduled on infra, or even master, nodes (TBD).
TeddyAndrieux added a commit that referenced this issue Oct 1, 2020
@TeddyAndrieux
salt: Tie calico-kube-controllers to master nodes
30eae01 
Tie `calico-kube-controllers` pod to master nodes only.
Since it's mandatory to have this pod to have a working cluster
let's tie this one to master and not to infra.

Fixes: #2243
TeddyAndrieux added a commit that referenced this issue Oct 1, 2020
@TeddyAndrieux
salt: Tie calico-kube-controllers to master nodes
dfda2ea 
Tie `calico-kube-controllers` pod to master nodes only.
Since it's mandatory to have this pod to have a working cluster
let's tie this one to master and not to infra.

Fixes: #2243
@TeddyAndrieux TeddyAndrieux mentioned this issue Oct 1, 2020
Merged
@bert-e bert-e closed this as completed in 7d3713c Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade Calico to 3.16.1 scality/metalk8s
1 participant
@NicolasT