kubernetes/minikube

dashboard: Add Node condition check (DiskPressure and pod status checks) before opening

Open

#5,815 opened on Nov 2, 2019

View on GitHub
 (50 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
co/dashboardco/none-driverhelp wantedkind/featurelifecycle/frozenpriority/important-longterm

Description

when i run it always hangs forever and sometimes throws 503

garretsidzaka@$$$$$:~$ sudo minikube dashboard

Verifying dashboard health ...
Launching proxy ...
Verifying proxy health ...

^C garretsidzaka@$$$$$:~$

garretsidzaka@$$$$$$:/usr/bin$ minikube version minikube version: v1.4.0 commit: 7969c25 ubuntu vm 1804 vm-driver=none

Contributor guide

Tech stack
go
Domain
frontendcli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingminikube internal architectureKubernetes node conditions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the minikube dashboard code to understand how it currently verifies cluster health. Look for existing checks for node conditions like DiskPressure. Review the conversation in the issue for any suggested approaches or prior attempts. Consider adding a preflight check that inspects node status and pod health before launching the dashboard proxy.