Open iamsaso opened 5 years ago
Currently, engineers need to create another service in codeamp that injects console to their project...
Ex. project checkr/deploy-test Service: web Deployed hash: f36274f
checkr/deploy-test
web
f36274f
When we deploy the project we create a new deployment named checkr-checkr-web inside production-checkr-deploy-test namespace
checkr-checkr-web
production-checkr-deploy-test
We cannot deploy a console service inside this namespace because we would delete it when we redeploy the service.
What we could do is create a second namespace production-checkr-console-deploy-test and create a deployment checkr-checkr-<release-id>-<created-at>
production-checkr-console-deploy-test
checkr-checkr-<release-id>-<created-at>
we could then give exec access to production-checkr-console-* namespace that would allow them to debug their code in production.
production-checkr-console-*
We could then run a task that would scale down and clean up old deployments...
Currently, engineers need to create another service in codeamp that injects console to their project...
Ex. project
checkr/deploy-testService:webDeployed hash:f36274fWhen we deploy the project we create a new deployment named
checkr-checkr-webinsideproduction-checkr-deploy-testnamespaceWe cannot deploy a console service inside this namespace because we would delete it when we redeploy the service.
What we could do is create a second namespace
production-checkr-console-deploy-testand create a deploymentcheckr-checkr-<release-id>-<created-at>we could then give exec access to
production-checkr-console-*namespace that would allow them to debug their code in production.We could then run a task that would scale down and clean up old deployments...