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

Have you tried passing `customTimeouts` through to the helm release resource via the component resource arguments?

here's a code snippet from something that we do:
```const chart = new k8s.helm.v3.Release(
      `opentelemetry-operator`,
      {
        name: 'opentelemetry-operator',
        chart: 'opentelemetry-operator',
        namespace: namespace.metadata.name,
        createNamespace: false,
        version: '0.27.0',
        values: {
          admissionWebhooks: {
            certManager: {
              enabled: false,
            },
          },
        },
        repositoryOpts: {
          repo: '<https://open-telemetry.github.io/opentelemetry-helm-charts>',
        },
      },
      {
        provider,
        customTimeouts: { create: '2m' },
      }
    );```

that will set the timeout in the pulumi program rather than at the chart level, hopefully that helps :slightly_smiling_face: