Back to all scenarios
Scenario #99
Cluster Management
K8s v1.20, Azure AKS
Unresponsive Dashboard Due to High Resource Usage
The Kubernetes dashboard became unresponsive due to high resource usage caused by a large number of requests.
Find this helpful?
What Happened
The Kubernetes dashboard was overwhelmed by too many requests, consuming excessive CPU and memory resources.
Diagnosis Steps
- 1Checked resource usage of the dashboard pod using kubectl top pod.
- 2Found that the pod was using more resources than expected due to a large number of incoming requests.
Root Cause
The dashboard was not scaled to handle the volume of requests.
Fix/Workaround
• Scaled the dashboard deployment to multiple replicas to handle the load.
• Adjusted resource requests and limits for the dashboard pod.
Lessons Learned
Ensure that the Kubernetes dashboard is properly scaled to handle expected traffic.
How to Avoid
- 1Implement horizontal scaling for the dashboard and other critical services.
- 2Monitor the usage of the Kubernetes dashboard and scale as needed.