Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

chore: add priorityClassName: system-node-critical to kube-system,… #555

Merged
merged 7 commits into from
Feb 27, 2019
Merged

chore: add priorityClassName: system-node-critical to kube-system,… #555

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
61ce143
chore: add priorityClassName: system-cluster-critical to kube-system,…
jackfrancis Feb 21, 2019
c1bddec
chore: copy/pasta error
jackfrancis Feb 21, 2019
3a29488
chore: prefer system-node-critical
jackfrancis Feb 21, 2019
a90f52a
chore: add’l tolerations for kube-proxy
jackfrancis Feb 21, 2019
acbca55
chore: add wildcard tolerations to ip-masq-agent, azure-cni-network-m…
jackfrancis Feb 25, 2019
0a4075a
chore: yaml whitespace how I love thee
jackfrancis Feb 25, 2019
c146f88
chore: whitespace
jackfrancis Feb 25, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions parts/k8s/addons/kubernetesmasteraddons-kube-proxy-daemonset.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ spec:
operator: Equal
value: "true"
effect: NoSchedule
- operator: "Exists"
effect: NoExecute
- operator: "Exists"
effect: NoSchedule
containers:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is to ensure that we never schedule kube-proxy on master, correct?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the opposite: it ensures that kube-proxy will always be able to be scheduled on any node, regardless of taint.

- command:
- /hyperkube
Expand Down