search

vmware-archive / octant

Highly extensible platform for developers to better understand the complexity of Kubernetes clusters.
https://octant.dev
Apache License 2.0
6.28k stars 488 forks source link

Improve Object Status #896

Open wwitzel3 opened 4 years ago

wwitzel3 commented 4 years ago

Design and implement a new view for object status with-in the resource viewer. This is some prior art on this that I will link to when I find it.

GuessWhoSamFoo commented 4 years ago

Possible cases to address with object status: https://github.com/cloudfoundry-incubator/kubernetes-guidelines

wwitzel3 commented 4 years ago

https://github.com/kubernetes-sigs/kustomize/blob/master/kstatus/status/status.go

wwitzel3 commented 4 years ago

This issue is going to start becoming very important.

As we work on the new resource viewer, lets keep this issue in mind. We want to be able to represent object states in a way that is meaningful. We can also considering holding the last 10 or some arbitrary amount of status in memory for the view. Allowing us to essentially create an object scoreboard. @mklanjsek How might we visualize that in resource viewer?

Also I know plugins would benefit from being able to set status and have it shown in a reliable and consistent way. So this is something you can think about as you explore the idea of a Falco plugin @GuessWhoSamFoo

Also thinking about CI/CD tooling which can have a wide range of status for various objects. Think of something that has failed but is being retried.

wwitzel3 commented 3 years ago

You may be interested in this issue @davidmirror-ops

mklanjsek commented 3 years ago

To make sure we are on the same page - I assume we are talking about kubernetes object status as defined here