ROX-20252: add rosa hcp option

[davdhacs]

Adds flavor option to infra for ROSA HCP.

[ghost]

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

CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.8.7-18-g4a505fc3dc to it.

🔌 You can connect to this cluster with:

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

[rhacs-bot]

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

CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.8.8-124-ga20dcf86b2 to it.

🔌 You can connect to this cluster with:

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

[tommartensen]

Should this parameter be exposed to the user?

[davdhacs]

I wasn't sure. I like showing that both ROSA flavors are the same, but with different default values. But it may just be confusing? I wondered if I should reset the ROSA flavor to be the same as it was before this change(?).

[tommartensen]

Yes, I think it is confusing now, because you could set Use Managed Control Plane to true in classic ROSA - what would the effect be?

[davdhacs]

Ok, you can change the arguments in the rosa flavor form to match the defaults in the hcp/hypershift form and you'll get a matching cluster. So it just provides different default settings, and the managed_cp toggles hypershift on/off.

[gavin-stackrox]

One minor nit/suggestion for help formatting, but otherwise LGTM.