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

When creating an EKS cluster via `@pulumi/eks` I need to specify some CNI env vars, such as `WARM_IP_TARGET` to decrease the pre-allocated pool of IP addresses.

How is that accomplished via Pulumi?

I'm trying to accomplish this:
<https://github.com/terraform-aws-modules/terraform-aws-eks/issues/96>

Interesting. I don’t think that this is currently possible with `@pulumi/eks`. Does this envvar need to be set on the worker nodes?

<@U84HBHXS8> I think the requirement here is actually deeper - it needs to be possible to deploy the CNI YAML prior to nodes being created, and to customize the env vars passed to the CNI daemonset as part of that deployment. My understanding is that this CNI yaml is deployed automatically by EKS, so would need to somehow be updated instead of created by the Pulumi component.  Definitely worth opening an issue on this to narrow down what the best extensibility point is to expose to enable this. 

<https://docs.aws.amazon.com/eks/latest/userguide/cni-upgrades.html>