ROX-17123, ROX-19217: Move GKEs to a RH project

[gavin-stackrox]

This PR switch GKE based flavors to a RH project. It:

• updates hardcoded project name refs
• surfaces the admin password for demo, qa-demo
• removes Auth0 for demo, qa-demo
• switches to a new domain for demos (demos.rox.systems) so that the complete provision could be tested on this PR without affecting production demos

See also: https://github.com/stackrox/automation-flavors/pull/151, the image links will be updated to a release tag once that merges.

Testing

Created one of each flavor using the PR infra instance. Verified access and in the case of demos that they 'look right'.

$ bin/infractl -k -e localhost:8443 list
gj-09-12-4 
  Flavor:      qa-demo
  Owner:       [email protected]
  Description: 
  Status:      READY
  Created:     26m ago
  Lifespan:    2d remaining
gj-09-12-2 
  Flavor:      demo
  Owner:       [email protected]
  Description: 
  Status:      READY
  Created:     1h0m ago
  Lifespan:    2d remaining
gj-09-11-1 
  Flavor:      gke-default
  Owner:       [email protected]
  Description: 
  Status:      READY
  Created:     18h ago
  Lifespan:    4d remaining

Note: CI is failing on this PR due to all the noise from test cluster creation. Once these clusters have expired I will destroy the PR infra instance and retest.

[ghost]

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

CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.7.11-27-g7e77d4088b to it.

🔌 You can connect to this cluster with:

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

❤️ for more specific service account credential names!

[BradLugo]

LGTM

[tommartensen]

LGTM.
FYI, I created https://issues.redhat.com/browse/ROX-19672, not sure if that was on your radar.