-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update error-code-poddrainfailure.md #1742
base: main
Are you sure you want to change the base?
Conversation
- Fixed prerequisites azure-cli version - Fixed the output error message and added another example (azure-cli output) - Added an example of restricted PDB and how to check the outputs - Added the commands for reconciliation/upgrade
@ffidelis : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit b73fedf:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md | Details |
support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md
- Line 26, Column 225: [Warning: insecure-link - See documentation]
Link 'http://aka.ms/aks/debugdrainfailures' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
- Line 29, Column 218: [Warning: insecure-link - See documentation]
Link 'http://aka.ms/aks/debugdrainfailures' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
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.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit 992215c:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md | Details |
support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md
- Line 26, Column 225: [Warning: insecure-link - See documentation]
Link 'http://aka.ms/aks/debugdrainfailures' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
- Line 29, Column 218: [Warning: insecure-link - See documentation]
Link 'http://aka.ms/aks/debugdrainfailures' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
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.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Fixed in the documentation http -> https error message. Nevertheless, that outputs came from the azure-cli output without the https protocol. It's been just copied the output and added in the documentation. Fixed the type <pod-nanme> -> <pod-name>
Learn Build status updates of commit 5c960ce: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
Learn Build status updates of commit 745edd6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
Small changes and adding documentation link to help clarify the topics
Learn Build status updates of commit dde163a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
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.