Bekir Dogan
Bekir Dogan
This is a very weird edge case about the currentRevision in the statefulsets: https://github.com/kubernetes/kubernetes/pull/106059#discussion_r743080306 kubectl-status should aim to explicitly report this case to increase the awareness about the "actual" status...
https://github.com/tilt-dev/kubectl-blame-examples provides a good perspective about different rollout tracking options. We could add support for different methods.
Push https://github.com/bergerx/kubectl-status/issues/199 further with these stretch goals for ingress checks: * the cert in the secret is not self-signed and must match the host * another ingress using the same...
This repo may be helpful to establish the first batch of tests: https://github.com/FalcoSuessgott/golang-cli-template
Currently, template development depends on developers. Kubernetes API has lots of fields optional and shows up only when there is a value is set. In many cases, they depend on...
In some cases, the certificate for ingress may be missing and it fallbacks to the default certificate. It would be good if we can catch these cases: * ingress should...
We can include the templates for the matching services for workload objects. Similar to the owners section we can have a matching services field in the output.
The current node output doesn't have any warning if the scheduling is disabled.
Querying services should be showing information on EndpointSlices as well. https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/