【问题标题】:EKS ingress controller creation not seeing tagged subnets?EKS 入口控制器创建没有看到标记的子网?
【发布时间】:2021-05-27 04:00:00
【问题描述】:

我是 EKS 新手,我正在按照示例设置一个示例应用程序,该应用程序从 How do I set up the ALB Ingress Controller on an Amazon EKS cluster for Fargate? 创建入口控制器、入口、服务和部署。我创建了所有内容(部署、pod、服务、iam、服务帐户等),但我的入口控制器未能提出错误

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"}

我确实根据Application load balancing on Amazon EKS 和其他显示如何标记我的 VPC 和子网的页面适当地标记了我的 VPC 和子网。

我有一个问题,我的入口清单有

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

【问题讨论】:

    标签: kubernetes kubernetes-ingress


    【解决方案1】:

    结果我不得不将标签添加到我的 VPC 的公共子网中,即使这是一个私有集群。

    【讨论】:

    • 与您的问题无关,但您是否注意到任何试图删除 alb.ingress.kubernetes.io/security-groups: sg-1234567890 中列出的安全组的日志?我遇到了stackoverflow.com/questions/66552105/… 中描述的这个问题并寻求帮助
    • @Vishal 我不必将安全组添加到我的入口控制器或入口资源。
    猜你喜欢
    • 2021-05-25
    • 1970-01-01
    • 1970-01-01
    • 2021-09-21
    • 1970-01-01
    • 1970-01-01
    • 2020-09-27
    • 1970-01-01
    • 2021-07-18
    相关资源
    最近更新 更多