Click shows pod in 'terminating' phase when kubectl shows 'unknown'

Open
  • Is something wrong?
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
kubernetes, rust
Domain
cli, devops

Research direction

Start by reading phase_str in src/cmd.rs around line 247 and compare its deletion-timestamp handling with the pod phase reported by kubectl. Done means a pod whose kubectl phase is unknown is shown as "unknown" rather than "Terminating", while the existing terminating behavior remains accurate for applicable pods.

Written by the indexing model from the issue text.

Description

When debugging a kubernetes issue using click, the phase for a pod was reported as "Terminating" when kubectl showed "unknown".

When debugging kubernetes issues, I prefer the most detailed info possible, so IMO it could be helpful to show the more precise "unknown" phase for the pod if possible.

The current behavior appears to be happening because click shows "Terminating" for any pod with a deletion timestamp. See phase_str.

Dominant language
Rust
Stars
1.5k
Forks
93
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/click

All issues in databricks/click

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.