Job pod name is not directly available in Workflow data from Argo Workflows v3.6.4, with Golang client

[gitfish77]

I am testing some very long task names against Argo Workflows v3.6.4.
Now I saw the Workflow data in the response under the status.nodes like:

        "job-cv162jjlc3t5ekbdguvg-4045790455": {
          "id": "job-cv162jjlc3t5ekbdguvg-4045790455",
          "name": "job-cv162jjlc3t5ekbdguvg.t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "displayName": "t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "type": "Pod",
          "templateName": "t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "templateScope": "local/job-cv162jjlc3t5ekbdguvg",
          "phase": "Succeeded",
          "boundaryID": "job-cv162jjlc3t5ekbdguvg",
          "startedAt": "2025-03-01T01:26:32Z",
          "finishedAt": "2025-03-01T01:26:44Z",
          "progress": "1/1",

None of the above fields matches the actual pod name:
job-cv0n201lsmlnuao3b5jg-t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567-4185117407

Surely I can try to construct the pod name by name.replace(".", "-").append(random_suffix_extracted_from_node_name).
Yet it is quite hacky and not future-proof for any pod format change from Argo Workflows.

My questions:
1] is there a recommended way to get the pod names for a running workflow?
My client version:
"github.com/argoproj/argo-workflows/v3/pkg/client/clientset/versioned/typed/workflow/v1alpha1"
2] To attack the issue from another angle: while my code is allowed to mutate the workflow spec, are there any approaches to enforce the base name of the the pods when submitting a workflow job? Or in the Argo Workflows deployment, e.g. in some configMap?
I saw another Argo Workflows v3.2 deployment which is included in Kubeflow Pipeline v2, where the job pods are always like "{UUID}-{random_suffix}". I checked their source code in Github and have not yet been able to figure out the trick.
One example of status.nodes from the Workflow data from KFP's Argo Workflows server, with consistent node name and id and pod name:

      "0451ea9f-ccb8-4cf3-9265-d1198a5862b6-2521202909": {
        "id": "0451ea9f-ccb8-4cf3-9265-d1198a5862b6-2521202909",
        "name": "0451ea9f-ccb8-4cf3-9265-d1198a5862b6.say-hello",
        "displayName": "say-hello",
        "type": "Pod",

I searched (GPT, Google, eetc) and spent a lot of time without success in trying with the following elements in the workflow manifest in the spec.templates:
podName, generateName, podSpecPatch, nodeName, metadata.generateName, metadata.name, etc.

Your help is highly appreciated!

[gitfish77]

I searched further and found this might be similar to #10107.
It looks like the v2 pod_names are still having issues.

[gitfish77]

Unblocked myself by enforcing the v1 pod naming and got the identical pod name with node id in the Workflows status.nodes data.
I have updated and rolled out the two deployments argo-workflows-server and argo-workflows-controller, by adding the following env to the containers:

        env:
        - name: POD_NAMES
          value: v1

One example of node in the status.nodes, with the actual pod name as "job-cv21j3rlc3t5ekbdgvf0-416961272":

        "job-cv21j3rlc3t5ekbdgvf0-416961272": {
          "id": "job-cv21j3rlc3t5ekbdgvf0-416961272",
          "name": "job-cv21j3rlc3t5ekbdgvf0.t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "displayName": "t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "type": "Pod",
          "templateName": "t123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-1234567",
          "templateScope": "local/job-cv21j3rlc3t5ekbdgvf0",
          "phase": "Succeeded",

[tczhao]

1] is there a recommended way to get the pod names for a running workflow?

You can get pod name using this function

2]

Yes, the pod_name v1 is a good solution for that

[gitfish77]

Thank you for the replies with the example code!