feat: add debug prep scripts and configuration for server #1104
Conversation
|
A single node development cluster (infra-pr-1104) was allocated in production infra for this PR. CI will attempt to deploy us.gcr.io/stackrox-infra/infra-server:0.8.8-9-g2bf3ef3d69 to it. 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: 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: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
| To debug the server, you need to fulfil the prerequisites first. | ||
|
|
||
| 1. Have an authenticated `gcloud` CLI. | ||
| 1. Have your `KUBECONFIG` point to a cluster where Argo Workflows and the ConfigMaps and Secrets for infra are deployed. This is most easily achieved by connecting to a PR cluster or deploying infra with `ENVIRONMENT=<DEVELOPMENT,PRODUCTION> make install-argo clean-argo-config helm-deploy` to a new or local cluster. This cluster will only be used to run workflows. |
There was a problem hiding this comment.
What about the infra-server deployment? I'm guessing this needs to be deleted so as not to conflict with the local dev server.
There was a problem hiding this comment.
No it doesn't have to be deleted. infra-server is stateless and all data is in Argo workflow K8s objects.
The point is that you can use the local debugging server against any existing infra cluster, ie also against dev & prod if you want to debug a bug 🐛
See README for usage.
Please test it before approving!
You can use
gcloud container clusters get-credentials infra-pr-1104 --zone us-central1-a --project acs-team-temp-devto point to a cluster with workflow controller and secrets prepared.