This message was deleted.

sparse-intern-71089

02/25/2021, 4:37 AM

This message was deleted.

billowy-army-68599

02/25/2021, 4:38 AM

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?

cuddly-actor-99406

02/25/2021, 4:43 AM

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

billowy-army-68599

02/25/2021, 4:51 AM

@cuddly-actor-99406 I opened an issue for it: https://github.com/pulumi/pulumi-eks/issues/544

👍 1

billowy-army-68599

02/25/2021, 6:08 AM

@cuddly-actor-99406 I think you can also solve this with the

aws.ec2.Tag

resource, trying something out

billowy-army-68599

02/25/2021, 6:40 AM

okay, this works!

Copy code

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

cuddly-actor-99406

02/25/2021, 8:33 AM

oh, cool. I'll try it out. Thankyou.

Open in Slack

Previous Next

Pulumi Community

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.