This repository has been archived by the owner on Oct 5, 2022. It is now read-only.
Increased AKS Node OS Disk Size #243
Closed
Conversation
This file contains 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
Increased disk size as disk saturation is occurring again when running Jenkins builds.
|
This is no longer required. We found that the issue causing DNS resolution failures was related to Tactical DNS server performance issues. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
JIRA link (if applicable)
AB#697
Change description
Increased the OS Disk Size for AKS Nodes. We believe that the current disk provisioned is the reason for DNS failures. According to the issue opened by MSFT below, Node OS Disk Saturation can have an impact on dns resolution. Increasing the disk size prompts Azure to spin up a disk with higher IOPS than the default one.
Azure/AKS#1373
Does this PR introduce a breaking change? (check one with "x")