This message was deleted.
# kubernetess
sparse-intern-71089
01/20/2021, 9:14 PMThis message was deleted.
w
wet-noon-14291
01/20/2021, 10:05 PMThis is super annoying, it happens about 30-50% of our deployments. The way we do it is like this:
1. Create args for a Deployment
2. Manipulate args until satisfied
3. Create Deployment resource with args
It almost looks like there is some kind of race condition since not all environment variables that we have defined in step 2 are added every time.
wet-noon-14291
01/20/2021, 10:36 PMDownloading the stack from the permalink defined in the deployment actually shows that the missing environment variables should be on the container... but then the provider might do something weird.
wet-noon-14291
01/20/2021, 10:37 PMnot sure though if that link is to what is being deployed or what is currently deployed.
c
cool-fireman-90027
01/21/2021, 12:53 PMHi Tomas,
Can you please open a git issue for this?
w
wet-noon-14291
01/21/2021, 1:28 PMsure, I don't know how to replicate a small case for it though, I can just write what we experience. I am also available to show what we see in our logs and show our code if needed.
👍 1
wet-noon-14291
01/21/2021, 3:06 PM@cool-fireman-90027 created https://github.com/pulumi/pulumi-kubernetes/issues/1442
wet-noon-14291
01/27/2021, 9:54 PMI'm sort of stuck with this super annoying issue: https://github.com/pulumi/pulumi-kubernetes/issues/1442.
Anyone that has experienced something similar? The issue is that the env variables we set on a k8s deployment, that references some k8s secrets, doesn't always seem to be included in the deploy. If we deploy again it might work some times, so it seems to be some kind of race condition or some weird transformation of the manifest that goes on.
4 Views