report node conditions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
If your pod is unschedulable, Tilt will show you the Kubernetes event on why it won't schedule:
[K8s EVENT: Pod example-html-749d4d9dbc-p8rtg (ns: default)] 0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.
but doesn't give you any hints on what to do next.
Tilt should give you a tool to help diagnose the problem. Usually you can figure out the problem by looking at kubectl describe nodes and looking at Conditions or Events to see what's blocking the Node becoming Ready
Additional context
This is similar in effect to the pod monitor that prints the stages of pod rollout
It would be nice to do this as an extension that you can install dynamically
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing pod monitor that prints rollout stages, then use the issue's suggested kubectl describe nodes workflow, focusing on node Conditions and Events. Done means Tilt provides a diagnostic tool or dynamically installable extension that helps explain why a node is not Ready and what may be blocking scheduling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100