add parameters to cluster output

[tommartensen]

This adds the workflow parameters to the Cluster message.
They can be displayed with the --json output flag.
That helps with debugging cluster issues.
Example in https://github.com/stackrox/infra/pull/1083/files#diff-a524488ef8b52930f6ae26541a6af3de9b82377d553b237639908ef9aa9d2f72R216-R227.

I am not sure if this will require a version bump (is changing the message of a proto a breaking change? I think it might not be because of compatibility promises)

[rhacs-bot]

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

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

🔌 You can connect to this cluster with:

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