:wave: sup yall. im a little stumped by some k8s /...
# kubernetes
f
šŸ‘‹ sup yall. im a little stumped by some k8s / helm + pulumi behavior, hoping someone might be able to shed light iā€™ve got a: ā€¢ custom ConfigMap resource, with a YAML string as the
data=
input (in a key) ā€¢ a helm chart resource, that takes ā˜ļø (
ConfigMap.id
) output in the
values=
input object iā€™m hoping to get one of the helm chart children resources (eg. a Pod) to update whenever the ConfigMap data value gets updated in our workflow - basically, hoping that they both get updated together based on the inputs/outputs docs, Iā€™m instantiating things in this order: 1. instantiating ConfigMap resource 2. assigning the output via apply()
Copy code
some_object["child_"resource"]["config_key"] = ConfigMap.id.apply(lambda v: v)
3. instantiating helm chart resource, and setting
value=some_object
ā€¦but when the ConfigMap data gets modified, I see ALL the helm resources just get
deleted
(not even replaced). but when the ConfigMap data is unchanged, everything is gravy. What might be the causing this? iā€™m getting lost in the various layers of abstraction
might be worth noting - iā€™m explicitly setting the ConfigMapā€™s
metadata.name
value, so my understanding is that the resource is immutable ā€” so Iā€™d expect this ā€œeverything deletedā€ behavior to happen 100% of the time, or 0% of the time
if there a ā€œcorrectā€ way to create a dependency between a ConfigMap + helm.Chart resource, so that when: ā€¢ the ConfigMap resource gets update/replaced ā€¢ the helm.Chart updates as well? iā€™ve tried passing the ConfigMap into the helm.Chartā€™s
depends_on=[ConfigMap]
arg, but to no avail