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

This does lead me to another thing though.. is there any way of ignoring such changes? I know it's possible to do ignoreChanges on a resource - but how do I match the underlying components in the helm chart? Basically I want to set a little flag that will state that typically I do not want to cycle these certs every single time I operate against the stack.. i.e. ignore akv2k8s/akv2k8s-envinjector-ca.data, etc..
```     ├─ kubernetes:<http://helm.sh/v3:Chart|helm.sh/v3:Chart>                                                 akv2k8s
 ++  │  ├─ kubernetes:core/v1:Secret                                                akv2k8s/akv2k8s-envinjector-ca    created replacement     [diff: ~data];
 ++  │  ├─ kubernetes:core/v1:Secret                                                akv2k8s/akv2k8s-envinjector-tls   created replacement     [diff: ~data];
 ~   │  ├─ kubernetes:apps/v1:Deployment                                            akv2k8s/akv2k8s-envinjector       updated                 [diff: ~spec]; Deployment initialization
 ~   │  └─ kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration>  akv2k8s/akv2k8s-envinjector       updated                 [diff: ~webhooks]```
How do I match that?