fix(aro): use default ARO worker type

[davdhacs]

The old pinned worker instance type has reduced availability in Azure and the new default is "v5" instead of "v3". We removed the pinned and are using the default in CI, let's do the same for Infra.

Tested with PR infra cluster and confirmed the az aro create arguments are correct in skipping the worker node type argument:
2025-11-03T16:29:14.193709606Z + az aro create --resource-group dh-11-03-because-white-raw --name dh-11-03-because-white-raw --vnet dh-11-03-because-white-raw --master-subnet master-subnet --worker-subnet worker-subnet --version 4.17.27 --fips false --worker-count 4 --pull-secret @/root/.redhat/pull-secret.txt --verbose

[rhacs-bot]

A single node development cluster (infra-pr-1697) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1697 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f