You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This pull request adds a new troubleshooting guide for Azure Kubernetes Service (AKS) users experiencing upgrade failures due to conflicting PodDisruptionBudgets (PDBs). The guide explains how to identify, resolve, and prevent issues where pods are covered by multiple PDBs, which can block node drains and cause upgrade failures.
New documentation for troubleshooting AKS upgrade failures:
Adds a comprehensive troubleshooting article (aks-eviction-autoscaler-troubleshooting.md) that covers:
How to recognize upgrade failures caused by pods matching multiple PDBs, including error message patterns and confirmation steps.
Step-by-step instructions for identifying and resolving conflicting PDBs, including commands to list, describe, and delete PDBs, and to verify pod health.
Multiple methods to retry or reconcile the upgrade after resolving the conflict, including CLI commands and backend reconciliation options.
Best practices to prevent future issues, such as ensuring each pod matches only one PDB and recommendations on PDB configuration.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.
Line 0, Column 0: [Suggestion: filename-incomplete - See documentation]The filename contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Line 0, Column 0: [Suggestion: filename-incomplete - See documentation]The filename contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
This PR contains added files. New files require human review.
File Change Percent
This PR contains file(s) with more than 30% file change.
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
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.
This pull request adds a new troubleshooting guide for Azure Kubernetes Service (AKS) users experiencing upgrade failures due to conflicting PodDisruptionBudgets (PDBs). The guide explains how to identify, resolve, and prevent issues where pods are covered by multiple PDBs, which can block node drains and cause upgrade failures.
New documentation for troubleshooting AKS upgrade failures:
aks-eviction-autoscaler-troubleshooting.md) that covers:Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.