Add code for Monitoring Windows AKS Node for failures #510
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.
Problem:
We have had ICMs in the recent past where Windows worker nodes on AKS were running into problems randomly during the course of their execution. To investigate these issues we need to collect logs/traces/events/dumps from the node immediately after the failure. This process has been cumbersome with challenges ranging from:
As a first step to solve this problem:
Then a scheduled task is created on the nodes using the "Monitoring Strategy" which was defined above.
example:
Register-ScheduledJob -Name "MonitorWindowsNode" -FilePath C:\k\debug\MonitorWindowsNode.ps1 -RunNow -ArgumentList "https://raw.githubusercontent.com/sbangari/SDN/MonitoringWindowsNode/Kubernetes/windows/debug/monitoring/strategies/CopyLogsToBlobStorage.psm1"
When the node goes into a faulted state as described by the strategy, logs are collected from the node. I also have a sample where these logs are automatically uploaded to Azure Blob storage.