Modify NodeNames in AWS jobs

[ronaldngounou]

Context

In the GCE jobs, the nodes are given well-defined names (like “us-east-1-a”) and so the per-node metrics have well-defined labels, so they can easily be compared across days. Whereas in the AWS job, the nodes seem to have randomly-assigned names, and so the metrics labels end up being different every day so we can't compare them as easily.

Example:

• NodeName in GCE test: name: control-plane-us-east1-b-jlvv, control-plane-us-east1-b-smv6
• NodeName in AWS test have different namings.

What you expected to happen:
The node metrics don't have consistent trends over time.

As a result, overtime GCE tests have a trend

https://perf-dash.k8s.io/#/?jobname=gce-5000Nodes&metriccategoryname=E2E&metricname=LoadResources&PodName=kube-proxy-nodes-us-east1-b%2Fkube-proxy&Resource=memory

AWS jobs don't have a trend because they are using different node names.
https://perf-dash.k8s.io/#/?jobname=aws-5000Nodes&metriccategoryname=E2E&metricname=LoadResources&PodName=kube-proxy-i-094de2c600c60d0bb%2Fkube-proxy&Resource=memory

Context in sig-scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1771436311523919

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ronaldngounou]

/assign