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

Add node taint to default node pool for scheduling system pods only #5

Open
SatyKrish opened this issue Nov 7, 2020 · 0 comments
Open

Add node taint to default node pool for scheduling system pods only #5

SatyKrish opened this issue Nov 7, 2020 · 0 comments
Assignees
@SatyKrish
Labels
enhancement New feature or request
Milestone
0.2

Comments

@SatyKrish
Copy link
Owner

You can add one or more system node pools to existing AKS clusters. It's recommended to schedule your application pods on user node pools, and dedicate system node pools to only critical system pods. This prevents rogue application pods from accidentally killing system pods. Enforce this behavior with the CriticalAddonsOnly=true:NoSchedule taint for your system node pools.

Microsoft Doc Link
@SatyKrish SatyKrish added the enhancement New feature or request label Nov 7, 2020
@SatyKrish SatyKrish added this to the 0.1.0 milestone Nov 7, 2020
@SatyKrish SatyKrish self-assigned this Nov 7, 2020
@SatyKrish SatyKrish modified the milestones: 0.1, 0.2 Nov 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SatyKrish SatyKrish

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.2
Development

No branches or pull requests
1 participant
@SatyKrish