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

image.png

related <https://pulumi-community.slack.com/archives/C84L4E3N1/p1699545394633679>

actually switching from Chart to Release does seem to fix the issue. yay!

The workaround for the Chart resource would be to use a transformation to set `ignoreChange` on the secret/certificate's data.

See here for an example of transformations:
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#chart-with-transformations|https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#chart-with-transformations>

try using it the aws.eks.addon
```export const csiAddon = new aws.eks.Addon(
  'aws-ebs-csi-driver-addon',
  {
    clusterName: eksCluster.name,
    addonName: 'aws-ebs-csi-driver',
    resolveConflictsOnUpdate: 'OVERWRITE',
    // addonVersion: 'v1.24.1-eksbuild.1',
  },
  { dependsOn: [eksCluster, nodeGroup] },
)```