ROX-28137: implement Janitor flavors hidden from users

[tommartensen]

Test it with infractl create janitor-delete-{gke-default, openshift-4, openshift-rosa} <cluster name>.

Prevents flavors with janitorDelete availability to show up on

• UI
• infractl flavor list
• infractl flavor get

Related: https://github.com/stackrox/automation-flavors/pull/310/files for fixes/improvements to the destroy functions.

[rhacs-bot]

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

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

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1534 --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

[davdhacs]

+1
This is great! And I think the concept of argo workflows matches well with ad-hoc 'janitor' cluster cleanup.