Failed build model due to couldn't auto-discover subnets: unable to discover at least one subnet

kubernetes-sigs / aws-load-balancer-controller

A Kubernetes controller for Elastic Load Balancers

https://kubernetes-sigs.github.io/aws-load-balancer-controller/

Apache License 2.0

3.93k stars 1.46k forks source link

Failed build model due to couldn't auto-discover subnets: unable to discover at least one subnet #3051

Closed dv000-7 closed 1 year ago

dv000-7 commented 1 year ago

Describe the bug

I am trying to deploy alb(ingress) . application is getting deployed but load balancer is not creating showing error "Failed build model due to couldn't auto-discover subnets: unable to discover at least one subnet. " Steps to reproduce

deploy eks cluster
helm repo add eks https://aws.github.io/eks-charts
kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master" 4.helm upgrade -i aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName= --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller

Expected outcome Normal SuccessfullyReconciled targetgroupbinding/k8s-default-appname-ad8ee871f8 Successfully reconciled but getting Warning FailedBuildModel ingress/appname Failed build model due to couldn't auto-discover subnets: unable to discover at least one subnet.

Environment

AWS Load Balancer controller version
Kubernetes version
Using EKS (yes/no), if so version?

Additional Context:

oliviassss commented 1 year ago

Hi, you need to set the clusterName, but you leave it empty in your command. Any specific reason?

dv000-7 commented 1 year ago

hello, i have given clustername in my cli helm upgrade -i aws-load-balancer-controller eks/aws-load-balancer-controller -n kube-system --set clusterName=testapp-cluster --set serviceAccount.create=false --set serviceAccount.name=aws-load-balancer-controller

oliviassss commented 1 year ago

Can you pls check if your subnets are properly tagged?

public subnets: kubernetes.io/role/elb: 1
private subnets: kubernetes.io/role/internal-elb: 1
common tag: kubernetes.io/cluster/${cluster-name}, with value owned or share

You can check our live doc for more ref: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/deploy/subnet_discovery/ Also some similar issue: https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/2812

Let me know if these can address your issue.

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

oliviassss commented 1 year ago

@dv000-7, I'm closing this issue as for now, please feel free to reach out or reopen if you have any questions. Thanks.