This message was deleted.
s
This message was deleted.
b
is it a public helm chart? it's not actually the case that a deployment would update when a secret changes, you need to do some little tricks to refresh the deployment
(I'm assuming here you're changing the secret values, not the secret name)
b
Not public, and yea, I need to do some little tricks but I'm not sure what 😶
I've tried to change both the keys and values inside the secret, but yea, didn't change the secret name itself
I'm not sure if that's a Pulumi limitation, on purpose or bug, but I'd expect it to change. What tricks would you recommend? 😶
b
it's kind of expected. the trick is to add an annotation to your deployment with the md5 hash of the contents of your secret. You can do this with Helm: https://github.com/elastic/helm-charts/blob/master/metricbeat/templates/deployment.yaml#L43 or pulumi: https://gist.github.com/jaxxstorm/c0fb80dacc7d293750ffbc5f1ace4527#file-index-ts-L51
b
Why "kind of expected"?
Thanks alot, looks like it's gonna fix it for now
b
the values inside the secret are only picked up at scheduling time for the pod. you have to restart the pod to pick up the new values
b
No, I get that, but Pulumi auto-updates the deployments when the secrets/configmaps change, so why wouldn't it do that with a deployment inside a helm chart?
Is that the expected behaviour or should I open an issue regarding that?
g
Just to clarify here: the reason it works for resources deployed natively with Pulumi is due to the resource dependency graph. This graph isn’t present within a Helm resource, which explains the lack of auto-update you’re seeing.