ROX-19609: add cluster name validation to infractl

[tommartensen]

This was a user request: https://issues.redhat.com/browse/ROX-19609.

$ bin/infractl-darwin-arm64 create gke-default this-name-is-way-too-loooooooooooooooooooooooooooooooooooooooong
NOTE: infractl no longer requires a NAME parameter when creating a cluster.
      If ommitted a name will be generated using your infra user initials, a
      short date and a counter for uniqueness. e.g. jb-10-31-1
Error: cluster name too long
$ bin/infractl-darwin-arm64 create gke-default t                                        
NOTE: infractl no longer requires a NAME parameter when creating a cluster.
      If ommitted a name will be generated using your infra user initials, a
      short date and a counter for uniqueness. e.g. jb-10-31-1
Error: cluster name too short
$ bin/infractl-darwin-arm64 create gke-default tFAISOFJAfsoi
NOTE: infractl no longer requires a NAME parameter when creating a cluster.
      If ommitted a name will be generated using your infra user initials, a
      short date and a counter for uniqueness. e.g. jb-10-31-1
Error: The name does not match the requirements. Only lowercase letters, numbers, and '-' allowed, must start with a letter and end with a letter or number.

[ghost]

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

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

🔌 You can connect to this cluster with:

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

Logs

Logs for the development infra depending on your @stackrox.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[gavin-stackrox]

🦇

[gavin-stackrox]

Gets the job done. Ideally the cluster flavor should tell infra how to validate the name but that plumbing does not exist.

[tommartensen]

Ideally the cluster flavor should tell infra how to validate the name but that plumbing does not exist.

Different requirements or allowed characters for different flavors might complicate the naming for users. I am in favor of keeping the current approach using the common denominator of allowed cluster names.
By the way, the validation logic is translated from the UI code at https://github.com/stackrox/infra/blob/master/ui/src/containers/LaunchClusterPage/ClusterForm.tsx#L43-L48