EKS ingress controller creation not seeing tagged subnets?

Question

I'm new to EKS, and am following the examples to set up a sample app that creates an ingress controller, ingress, service, and deployment from How do I set up the ALB Ingress Controller on an Amazon EKS cluster for Fargate?. I have everything created (deployements, pods, service, iam, service account, etc.) but my ingress controller is failing to come up with the error

E0224 19:09:07.053006       1 controller.go:217] kubebuilder/controller "msg"="Reconciler error" "error"="failed to build LoadBalancer configuration due to retrieval of subnets failed to resolve 2 qualified subnets. Subnets must contain the kubernetes.io/cluster/\u003ccluster name\u003e tag with a value of shared or owned and the kubernetes.io/role/elb tag signifying it should be used for ALBs Additionally, there must be at least 2 subnets with unique availability zones as required by ALBs. Either tag subnets to meet this requirement or use the subnets annotation on the ingress resource to explicitly call out what subnets to use for ALB creation. The subnets that did resolve were []"  "controller"="alb-ingress-controller" "request"={"Namespace":"mynamespace","Name":"2048-ingress"}

I do have my VPCs and subnets tagged appropriately per Application load balancing on Amazon EKS and other pages that shows how to tag my VPCs and subnets.

One question I have, my ingress manifest has

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: "2048-ingress"
  namespace: "mynamespace"
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip

Chris F Chris F · Accepted Answer · 2021-03-03T18:58:14

So it turns out I had to add the tags to the public subnets of my VPC, even though this is a private only cluster.

EKS ingress controller creation not seeing tagged subnets?

1 Answers