Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Daemonset incorrectly shows "Ok" with green check when # of Ready pods != Desired #1565

Closed
bbgobie opened this issue Oct 29, 2020 · 0 comments · Fixed by #2389
Closed

Daemonset incorrectly shows "Ok" with green check when # of Ready pods != Desired #1565

bbgobie opened this issue Oct 29, 2020 · 0 comments · Fixed by #2389
Labels
api enhancement New feature or request

Comments

@bbgobie
Copy link

bbgobie commented Oct 29, 2020

What steps did you take and what happened:
View from overall summary and Daemon Sets page is showing daemonset with green checkmark and "OK" status when hovered over. However here is the output from Kubectl which Octant agrees with.

kube-proxy 46 46 45 1 45 beta.kubernetes.io/os=linux 90d

What did you expect to happen:
A red X or something to clearly show that something is wrong with the daemonset. For example Alertmanager is sending alerts, Octant if used as an operational dashboard needs to be able to clearly and concisely show which resources have issues.
Anything else you would like to add:
Ideally resources not ready default to the top of lists, eg pod list of this daemonset

Environment:

  • Octant version (use octant version): Version: 0.16.1
    Git commit: 8aebb34
    Built: 2020-10-07T23:36:32Z
  • Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.9", GitCommit:"a34b0bfd73e1e6b618969df59dfd8bbfdd1e0711", GitTreeState:"clean", BuildDate:"2020-09-17T06:35:17Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
  • OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Windows 10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants