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

Also curious why <https://www.pulumi.com/blog/persisting-kubernetes-workloads-with-amazon-efscsi-volumes-using-pulumi-sdks/#step-3-create-the-csi-driver-node-and-controller-components|that article> doesn't use the CSI driver helm better for long term maintainance. Does that Pulumi code do something different than the efs csi driver helm chart?

Or even something like this:
```new k8s.yaml.ConfigFile("aws-efs-csi-driver", {
    file: "<http://github.com/kubernetes-sigs/aws-efs-csi-driver/deploy/kubernetes/overlays/stable/?ref=master|github.com/kubernetes-sigs/aws-efs-csi-driver/deploy/kubernetes/overlays/stable/?ref=master>",
}, {
    provider: k8sProvider,
});```

I wasn’t directly involved with that article, but I think the author’s intent was to show how to do that with native Pulumi code. I don’t recall there being a deeper functional reason to do so if the YAML or Helm is working for you

Any idea what is with the format of that URL? AWS uses it all over <https://github.com/kubernetes-sigs/aws-efs-csi-driver#installation|their docs> but it is a 404 via the browser. Using the above code doesn't work for, presumably, that reason.  