Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Degraded status on jobs in workloads #2720

Closed
strowk opened this issue May 27, 2024 · 0 comments · Fixed by #2729
Closed

Degraded status on jobs in workloads #2720

strowk opened this issue May 27, 2024 · 0 comments · Fixed by #2729

Comments

@strowk
Copy link

strowk commented May 27, 2024




First of all, great work on new features you added this year. I was just trying out the new Workload feature and noticed on our cluster a lot of degraded pods that were created by our cronjobs, which I believe are actually ok. More details further.

Describe the bug
When cronjob creates jobs, by default it keeps 3 successful ones and their pod as well. Successful runs usually have pod in Completed status. However, k9s shows them in Workloads as Degraded (I assume derived from number of running pods?).

To Reproduce
Steps to reproduce the behavior:

  1. Create cronjob ( this one should work)
  2. Wait until it runs couple times.
  3. Open k9s and go to Workloads
  4. See that pods related to jobs are shown as DEGRADED.

Expected behavior
Expected status of pods related to finished jobs to be OK or COMPLETED or anything not demanding attention and differently colored than red/orange (maybe same color as Completed pods?)

Screenshots
Unsaved Image 1

Versions (please complete the following information):

  • OS: Ubuntu 20.04
  • K9s: v0.32.3
  • K8s: v1.29.4-eks-036c24b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant