kubectl-status
kubectl-status copied to clipboard
bergerx
A kubectl plugin to print a human-friendly output that focuses on the status fields of the resources in kubernetes.
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...
E.g. if the deployment is experiencing an outage, include its pods' statuses in the output.
If a pod is down for whatever reason, include the last N (10?) lines of the recently terminated container. These could also be helpful for initContainers if they block the...
Currently, we only color-code it based on the status field value. But the status field conventionally has one of these 3 values: "True", "False", "Unknown". The current behavior is to...