chore(toil improvement): add script to find demo clusters for obscurely named VMs

[tommartensen]

Some VMs from our manual GCP VM check have weird names that are not obvious matches to infra clusters.
They come from the demo flavor.
This very basic script finds the infra cluster that owns these resources.

Example: ./scripts/orphan-clusters/find-demo-clusters-for-vms.sh ztdlgvpq

TODO:

• update the weekly reminder to use this script to find demo clusters for weird VM names

[rhacs-bot]

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

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

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1412 --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 install-local

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