This message was deleted.

If you just using the AWS ALB Ingress controller, you should just need to label your subnets with kubernetes.io/role/eb1=1, or kubernetes.io/role/internal_elb=1, shouldn't need the cluster name in the tags. Then in your ingress controller config you utilize autodiscovery.

I see… I’ll give it a try.. I was getting this error:

"error"="failed to build LoadBalancer configuration due to failed to resolve 2 qualified subnet with at least 8 free IP Addresses for ALB. Subnets must contains these tags: '<http://kubernetes.io/cluster/prod-3a363ad|kubernetes.io/cluster/prod-3a363ad>': ['shared' or 'owned'] and '<http://kubernetes.io/role/elb|kubernetes.io/role/elb>': ['' or '1'].

which suggests I need both. but maybe that’s misleading

Interesting the documentation must have changed. I have since moved away from EKS. If that is the case, if you have a naming convention you are using for the cluster you could always "template" that in.

yeah, the problem is that the cluster needs the subnet ids. and then the subnet ids need the cluster physical name. i can “hard-code” (by specifying the physical name when creating the cluster), but i’d rather not

I dont think there is a way outside of templating based off your naming conventions.

$"{environment}-{service}-k8

looks like i can probably use a `Tag`: https://www.pulumi.com/docs/reference/pkg/aws/ec2/tag/

Let me know if that works, per the docs its only for Ec2 Instances.

It worked.. but it's kind of unreliable. I needed to add multiple tags, and sometimes it seemed like the ones that were added later overwrote the ones added first. Only when I added them all at the same time, did it work 😒