Fix NodeNames aggregation 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 GCE tests truncate the last 4 characters when aggregating.
• NodeName in AWS test have different namings. They contain the instance-id in the name.

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-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale