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.

Pulumi Community

I think a transformation is your answer here, but it means you might need to remove the fields one by one.

<@UDEJ1F5SQ> That would be a pain in the ass because used in multiple places.
It would be nice to support this somehow from pulumi.

Not sure I follow in terms of "multiple places" - can you elaborate?

In the traefik helm chart the `.Values.metrics` condition used in multiple places, e.g.: deployment "ports" section, command-line arguments, etc.
That's why I said it's hard to remove from everywhere with transformations, it's possible of course, but wouldn't be a maintainable code (e.g.: a next helm chart version adds more sections based on the same condition)