Deploy Boards manifest file for K8s doesn't pass through env variables
Problem to solve
The example manifest file for enabling Deploy Boards doesn't take into account that env vars don't work inside deployment files if used through kubectl directly.
This means that if someone were to use the exact deployment file and use a script in a CI/CD job that does kubectl apply -f deployment.yaml
, the variables won't be substituted and will be literal ${CI_PROJECT_PATH_SLUG}
in the actual deployment instead of the expected value. This will prevent Deploy Boards from showing up in a project's environment.
Proposal
Based on the Kubernetes issue, I believe we'd need to add a note/warning that it won't work through kubectl apply and you need to rely on something else (small custom script maybe) to substitute the variables in the deployment file, though I'm not sure if I'm missing anything here, and the issue is relatively old, it may be something else at play that happened here.
Who can address the issue
Would love some feedback from people more experienced with Kubernetes.
Other links/references
Encountered by Premium customer in ZD (internal only).