Azure support in perf-tests and on the dashboard

[mboersma]

What would you like to be added:

We would like to add an Azure-based job to the Kubernetes performance dashboard.

Why is this needed:

Another provider in the mix will increase the information available to the Kubernetes community and broaden the test signal available to maintainers and to the release team.

Changes to ClusterLoader2 perf and scalability tests are anticipated, so this seemed a reasonable place to track the effort.

Details:

This is a tracking issue and is purposefully short on detail. We are in the investigation phase currently, and we very much appreciate all the help we've gotten from sig-scalability folks so far!

[mboersma]

/cc @jackfrancis @Jont828

[jackfrancis]

/assign @mboersma @Jont828

[jackfrancis]

This PR proposes a new Azure 100 node scale test:

• Add job to run ClusterLoader2 load test on 100 node CAPZ cluster test-infra#33423
  This PR proposes we rename the clusterloader2 "aks" provider to "azure":
• Rename AKS provider to Azure #2864

[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

[mboersma]

/remove-lifecycle stale

[jackfrancis]

Now that kubernetes/test-infra#33423 has landed we can close this!

/close

[k8s-ci-robot]

@jackfrancis: Closing this issue.

Details

In response to this:

Now that kubernetes/test-infra#33423 has landed we can close this!

/close

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.