简体   繁体   English

如何在kops在AWS上安装的k8s集群中使用alb-ingress-controller?

[英]How to use alb-ingress-controller in k8s cluster which installed by kops on AWS?

Want to use alb-ingress-controller on AWS. 想要在AWS上使用alb-ingress-controller

Have installed k8s cluster by kops . kops安装了k8s集群。

Followed this guide use alb-ingress-controller : 按照本指南使用alb-ingress-controller

https://github.com/coreos/alb-ingress-controller/blob/master/docs/walkthrough.md https://github.com/coreos/alb-ingress-controller/blob/master/docs/walkthrough.md

When check logs after run $ kubectl apply -f echoserver-ingress.yaml , 在运行$ kubectl apply -f echoserver-ingress.yaml之后检查日志时,请$ kubectl apply -f echoserver-ingress.yaml

$ kubectl logs -n kube-system \
$(kubectl get po -n kube-system | \
egrep -o alb-ingress[a-zA-Z0-9-]+) | \
egrep -o '\[ALB-INGRESS.*$' | \
grep 'echoserver\/echoserver'

[ALB-INGRESS] [echoserver/echoserver] [ERROR]: Error parsing annotations: Retrieval of subnets failed to resolve 2 qualified subnets. Subnets must contain the tag:kubernetes.io/cluster/cluster01.orange-test.dev.drecom.jp tag with a value of shared and the tag:kubernetes.io/role/alb-ingress tag signifying it should be used for ALBs Additionally, their 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 []. (cache hit)

I have set two subnets in every unique AZ for one special VPC. 我为一个特殊的VPC在每个唯一的可用区中都设置了两个子网。 And set cluster name's value to shared , added a kubernetes.io/role/alb-ingress . 并将集群名称的值设置为shared ,添加了kubernetes.io/role/alb-ingress Why can't pass it? 为什么不能通过?

Did you add tags to your subnets ? 您是否在子网中添加了标签?

In the walkthrough it says: 在演练中它说:

... ...

  1. Add tags to subnets where ALBs should be deployed. 将标签添加到应在其中部署ALB的子网。

... ...

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM