Create blog post on AKS NAP disruption management#5685
Open
wdarko1 wants to merge 3 commits intoAzure:masterfrom
Open
Create blog post on AKS NAP disruption management#5685wdarko1 wants to merge 3 commits intoAzure:masterfrom
wdarko1 wants to merge 3 commits intoAzure:masterfrom
Conversation
Added a blog post on managing disruption with AKS Node Auto-Provisioning, covering best practices for Pod Disruption Budgets and consolidation.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new AKS blog post focused on managing voluntary disruption when using Node Auto-Provisioning (NAP), with guidance on Pod Disruption Budgets (PDBs), consolidation controls, disruption budgets, and maintenance windows.
Changes:
- Added a new blog post covering NAP disruption concepts and common pitfalls.
- Included YAML examples for PDBs and NodePool disruption settings (consolidation policy, budgets, schedules).
- Added operational guidance on observability and drift/image update considerations.
Comment on lines
+26
to
+34
| --- | ||
|
|
||
| <!-- truncate --> | ||
|
|
||
| :::info | ||
|
|
||
| Learn more about how to [configure disruption policies for NAP](https://learn.microsoft.com/azure/aks/node-auto-provisioning-disruption) | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Per the repo’s blog post structure, add a hero image immediately after <!-- truncate -->. The post directory currently contains only index.md, so readers won’t get a hero/social image unless you add one (for example ./hero-image.png) and reference it here with descriptive alt text.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
|
||
| **Fix** | ||
| - Relax PDBs (for example `maxUnavailable: 1`) or increase replicas. | ||
| - If a workload truly must be undisruptable, accept that nodes running it won’t be good consolidation targets. |
There was a problem hiding this comment.
Spelling: “undisruptable” should be “undisruptible” (or rephrase to “cannot be disrupted”).
Suggested change
| - If a workload truly must be undisruptable, accept that nodes running it won’t be good consolidation targets. | |
| - If a workload truly must not be disrupted, accept that nodes running it won’t be good consolidation targets. |
Clarified descriptions of Pod Disruption Budgets and their impact on voluntary evictions. Improved wording for clarity and corrected minor typos.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a blog post on managing disruption with AKS Node Auto-Provisioning, covering best practices for Pod Disruption Budgets and consolidation.