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

At this time, I'd stick to using the <https://www.pulumi.com/registry/packages/aws/|AWS Classic provider> as the AWS Native provider lacks quite of bit of AWS surface area due to AWS Cloud Control API lacking the surface area.

The one caveat is AWS Native does gain same day support for new AWS services released. In this case, AWS Native can be a good choice (assuming it also exists in AWS Cloud Control API).

I haven't had an issue with coverage.   My issues have been with functionality.

The preview feature breaks if you change anything about the cluster.

Updating addons doesn't work if you have to use the overwrite option for ResolveConflicts

Changing the node group size just breaks because Pulumi thinks it can update it, but it needs to replace the node group instead.

Tonight, I'm upgrading some clusters and while it is working, it is not really handling the order of operations properly, even though I have dependencies setup correctly (I think).   As a result, I'm having to run update multiple times to get it to go through all the steps.

AWS classic is by far the more battle hardened and more used provider. I'd stick with that provider.