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

It solves the problem that the cloud node configuration taint causes the pod of yurt controller manage to be unable to schedule to the cloud node #299

Merged
merged 1 commit into from
May 13, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions config/setup/yurt-controller-manager.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,8 @@ spec:
spec:
serviceAccountName: yurt-controller-manager
hostNetwork: true
tolerations:
- operator: "Exists"
affinity:
nodeAffinity:
# we prefer allocating ecm on cloud node
Expand Down
2 changes: 2 additions & 0 deletions config/yaml-template/yurt-controller-manager.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,8 @@ spec:
spec:
serviceAccountName: __project_prefix__-controller-manager
hostNetwork: true
tolerations:
- operator: "Exists"
affinity:
nodeAffinity:
# we prefer allocating ecm on cloud node
Expand Down
2 changes: 2 additions & 0 deletions pkg/yurtctl/constants/constants.go
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,8 @@ spec:
spec:
serviceAccountName: yurt-controller-manager
hostNetwork: true
tolerations:
- operator: "Exists"
affinity:
nodeAffinity:
# we prefer allocating ecm on cloud node
Expand Down