[15:48:22] <brouberol>	 passing thought. Our `base.meta.pod_annotations` template contains `checksum/secrets: {{ include (print $.Template.BasePath "/secret.yaml") . | sha256sum }}`, which checksums the content of the whole secret.yaml template. This means that when we bump the chart version, the checksum changes, because the label changes
[15:48:57] <brouberol>	 not only this isn't ideal for review, as we might wonder why is the Secret changing when it's not, but it'll also cause pod rolling restarts, as the Deployment spec changes
[15:49:15] <brouberol>	 I've been experimenting locally with the following replacement
[15:49:15] <brouberol>	 checksum/secrets: {{ toString (get (fromYaml (tpl (include (print $.Template.BasePath "/secret.yaml") .) .)) "data") | sha256sum }}
[15:49:42] <brouberol>	 it basically renders the secret.yaml template, load it as a object, renders the .data field into a string and checksums it 
[15:49:57] <brouberol>	 meaning that the checksum will only change when the Secret _content_ changes
[15:50:28] <brouberol>	 I'm reaching out here before going anywhere else with this. Is that something we'd want, or are we happy with the current behvior?
[15:51:05] <brouberol>	 sorry, in my first message, I should have said "because the `chart` label changes"
[15:52:15] <jayme>	 that's something that keeps bugging me but I never came around to crafting the above horror - also some extra caution needs to be taken on a per chart basis as the secret.yaml may contain more then one document etc.
[15:52:50] <jayme>	 (or you'd have to extend the horror to support multi document yaml :))
[15:53:40] <brouberol>	 that is indeed correct. Some more horror can probably be layered on top of the existing horror
[15:54:08] <brouberol>	 but implementation kept aside, would that be a default behavior we'd like?
[15:54:44] <jayme>	 yes, absolutely
[15:55:19] <jayme>	 there might be some weird case that relies on the current behaviour - but that's at fault then anyways
[15:55:47] <brouberol>	 alright then, I'll work on that for our airflow chart and will try to "upstream" the solution to our templates
[15:55:50] <brouberol>	 thanks!
[15:56:56] <jayme>	 nice, thanks!
[16:28:29] <akosiaris>	 that's the chartid thing right? that we have in both configmaps and secrets
[16:52:51] <brouberol>	 akosiaris: I'm not sure I understand
[16:53:26] <brouberol>	 (I was able to do what I wanted, but it's not a one liner. I consider that an added bonus. I'll send the patch tomorrow)