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

there's no easy I've come up with doing it, generally I just give the cluster a known name. I'm assuming this is for the subnet tags eks needs to provision loadbalancers?

you assume correctly : ) A known name is good solution, haha. I'll go with that. Thanks.

<@U01KXJQMKAA> I opened an issue for it:
<https://github.com/pulumi/pulumi-eks/issues/544>

<@U01KXJQMKAA> I think you can also solve this with the `aws.ec2.Tag` resource, trying something out

okay, this works!

```vpc.privateSubnetIds.then(id =&gt; id.forEach((id, index) =&gt; {
    new aws.ec2.Tag(`subnettag-${index}`, {
        key: cluster.eksCluster.name.apply(name =&gt; `<http://kubernetes.io/cluster/${name}`|kubernetes.io/cluster/${name}`>),
        resourceId: id,
        value: "owned",
    })
}))```