Bekir Dogan

It would be good to know if a pod is on a node that is actively under pressure (or has recently been under pressure) when checking pods.

We have been suffering from https://github.com/kubernetes/kubernetes/pull/78709 for a while. Once an existing statefulset is deployed with some faulty config, there seems to be no way to get it to recover...

If a resource has an owner defined in the metadata.ownerReferences list but it doesn't exist, there should be a visible warning. See https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/ for more details.

Users may be confused with inconsistent outputs of the same command on different environments. kubectl-status tries to query and incorporate information from related resources (e.g. `Kind: NodeMetrics` are included to...

Also showing a diff would a big plus, but just having a drift's existence is already a huge gain.

More details in https://github.com/kubernetes-sigs/krew-index/pull/526#issuecomment-595565045

We are not using parallel jobs (https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#parallel-jobs). If you are experienced on using parallel jobs please take a look at the "job_parallel" template.

If you are actively using ResourceQuotas please think about contributing because we don't yet use ResourceQuotas actively. Our knowledge on its details is quite limited.

Currently describe prints the below details when querying a node. But the real-time utilization is missing in that picture. ``` Non-terminated Pods: (12 in total) Namespace Name CPU Requests CPU...