What you would like to be added?
Pod clique set and pod clique scaling group indexes are added to each pod name in order to disambiguate their naming. I would like the pod clique index to also be part of the pod name.
Why is this needed?
When investigating a pod failure that includes the hostname, such as ubuntu-0-worker-0, it isn't possible to easily pinpoint the actual pod name to debug:
$ kubectl get po
NAME READY STATUS RESTARTS AGE
ubuntu-0-worker-2tnab 1/1 Running 0 7h41m
ubuntu-0-worker-5mfde 1/1 Running 0 7h41m
Custom columns can help, but require additional tools or aliases and don't work with standard options like -o wide:
$ kubectl get pods -o custom-columns=NAME:.metadata.name,INDEX:'.metadata.labels.grove\.io/podclique-pod-index',STATUS:.status.phase
NAME INDEX STATUS
ubuntu-0-worker-2tnab 0 Running
ubuntu-0-worker-5mfde 1 Running
Ideally, adding the pod clique pod index would make it easier to pinpoint the exact pod:
$ kubectl get po
NAME READY STATUS RESTARTS AGE
ubuntu-0-worker-0-2tnab 1/1 Running 0 7h41m
ubuntu-0-worker-1-5mfde 1/1 Running 0 7h41m
What you would like to be added?
Pod clique set and pod clique scaling group indexes are added to each pod name in order to disambiguate their naming. I would like the pod clique index to also be part of the pod name.
Why is this needed?
When investigating a pod failure that includes the hostname, such as
ubuntu-0-worker-0, it isn't possible to easily pinpoint the actual pod name to debug:Custom columns can help, but require additional tools or aliases and don't work with standard options like
-o wide:Ideally, adding the pod clique pod index would make it easier to pinpoint the exact pod: