flaky-plumber-11624
08/09/2023, 11:15 PMℹ deploy.gdp-garden [verbose] → [kubernetes-plugin] Status of Deployment dp-ci-1691586975313-gdp is "deploying"
⚠ deploy.gdp-garden → Deployment/dp-ci-1691586975313-gdp: Error: failed to generate container "5619a71419b472824c14778e2632e2ed39f0571748f98e54023cf05c87e231cf" spec: failed to generate spec: no command specified
ℹ deploy.gdp-garden [verbose] → [kubernetes-plugin] Deployment/dp-ci-1691586975313-gdp: Error: failed to generate container "5619a71419b472824c14778e2632e2ed39f0571748f98e54023cf05c87e231cf" spec: failed to generate spec: no command specified
A CMD is present inside the Dockerfile to build the container used in this deployment, so our helm chart does not have any command specified for the deployment, and it has always worked in the past (and when I deployed the chart locally using garden). I could add a command to the manifest or helm values to bypass this error. But I am wondering why there is a difference in behaviors. Am I missing some permission in the ClusterRole?
https://cdn.discordapp.com/attachments/1138973829117526106/1138973829255933962/clusterrole.png▾
swift-garage-61180
08/11/2023, 11:43 AMcluster-buildkit
or kaniko
build modes might be useful to narrow this down (from your description, I got the impression you're doing local Docker builds both in CI and in dev).
This way, you'd get the same build behaviour in dev and CI (since both would be doing in-cluster builds in the remote cluster).
If there's still a problem with the deployment at that point, then maybe that helps narrow this down a bit.