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 looked at the pulumi-eks provider? It should be able to handle most of this, e.g.: <https://github.com/pulumi/pulumi-eks/blob/4f4a75b17de98cf2f9c3d34a960b59503cbc4f0a/python/pulumi_eks/vpc_cni.py#L21>

I’m currently using it - but i’m doing the VPC CNI outside of it, because I needed to upgrade the VPC CNI in order to use SecurityGroups for pods?

also as I;’ve been using it, I’ve kinda been starting to agree with this Issue: <https://github.com/pulumi/pulumi-eks/issues/592>

Yeah sadly this gets a bit ugly. You could either try importing the daemonset into pulumi and updating the environment variable in the spec or use a <https://www.pulumi.com/docs/intro/concepts/resources/#dynamicproviders|dynamic provider> to set it on the existing daemonset - essentially wrapping kubectl command you mentioned…