https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
b
r
How would I apply that to a component of a chart resource? Are each sub-resource inside of a chart identifiable in a way?
I ended up switching from using 
helm.v3.Chart
in 
@pulumi/helm
to using 
k8s.helm.v3.Release
in 
@pulumi/kubernetes
and it fixed my problem.
Seems like generally 
k8s.helm.v3.Release
is a bit more developed than 
helm.v3.Chart
, considering the latter doesn’t have hook support.
g
A pitty I saw this late, the similar question comes too often and 
v3.Release
resolves the most problems. I guess it would be good to have some information in the docs.
🙏 1
l
@rich-motorcycle-98689 good to hear the 
Release
resource solved it for you. In case you want to use 
Chart
again in the future, @billions-xylophone-85957 was on the right track to propose the 
ignoreChanges
resource property. You can apply this to a 
Chart
resource using a resource transformation. See the 
Chart with Transformations
example here: https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#chart-with-transformations
r
Ohhh, interesting. So you’d add the 
ignoreChanges
to a resource transformation in order to apply it to a specific resource. I guess in my case it would be as simple as applying it to all 
Secret
and 
MutatingWebhookConfiguration
resources (since I only had those resources that were causing a problem).
Would it be fair to characterize the difference between the 
Release
and the 
Chart
as the 
Release
being an OOTB helm solution, while the 
Chart
allows for extremely fine-grained configuration control? Because it seems like the 
Transformations
tool could be extremely powerful, esp for performing chart manipulation beyond what is configurable in the chart’s 
values.yaml
, and I don’t see an option for transformations in the 
Release
resource.
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by