RS-574: Deploy dev infra to the PR development cluster

[gavin-stackrox]

#710 creates the cluster and this PR is a follow up to deploy PR changes to this development cluster. It is more involved than it might have been because I wanted to avoid the creation of local configuration with opaque secrets when deploying with CI.

The main change in order to avoid local filesystem writes was to consolidate all the credential files under chart/infra-server/configuration/{development,production} into helm values files that can be piped to template rendering.

Testing Performed

A qa-demo cluster with a private rhacs-eng image:

bin/infractl -k -e localhost:8443 create qa-demo gj-20221007-2 --arg main-image=quay.io/rhacs-eng/main:3.72.x-253-g49e0fb76dc --wait --lifespan=1h

An osd-gcp cluster:

bin/infractl -k -e localhost:8443 create osd-on-gcp gj-20221007-osdgcp --wait --lifespan=2h

[ghost]

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

CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.4.0-22-g694d32f7c3 to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-711 --zone us-central1-a --project srox-temp-dev-test

🛠️ 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 local-data-dev-cycle

[davdhacs]

LGTM
The comment formatting is a nit.

[tommartensen]

You might consider setting this env var in line 93.

[tommartensen]

LGTM, one small hint about env var.