简体   繁体   English

AWS EKS 入口 - 无地址

[英]AWS EKS Ingress - No Address

I have a kubernetes application using AWS EKS.我有一个使用 AWS EKS 的 kubernetes 应用程序。 With the below details:带有以下详细信息:

Cluster: + Kubernetes version: 1.15 + Platform version: eks.1集群:+ Kubernetes 版本:1.15 + 平台版本:eks.1

Node Groups: + Instance Type: t3.medium + 2(Minimum) - 2(Maximum) - 2(Desired) configuration节点组:+ 实例类型:t3.medium + 2(最小)- 2(最大)- 2(所需)配置

[Pods] + 2 active pods [吊舱] + 2 个活动吊舱

[Service] + Configured Type: ClusterIP + metadata.name: k8s-eks-api-service [服务] + 配置类型:ClusterIP + metadata.name:k8s-eks-api-service

[rbac-role.yaml] https://pastebin.com/Ksapy7vK [rbac-role.yaml] https://pastebin.com/Ksapy7vK

[alb-ingress-controller.yaml] https://pastebin.com/95CwMtg0 [alb-ingress-controller.yaml] https://pastebin.com/95CwMtg0

[ingress.yaml] https://pastebin.com/S3gbEzez [ingress.yaml] https://pastebin.com/S3gbEzez

When I tried to pull the ingress details. Below are the values (NO ADDRESS)
Host: *
ADDRESS: 

My goal is to know why the address has no value.我的目标是知道为什么地址没有价值。 I expect to have private or public address to be used by other service on my application.我希望我的应用程序中的其他服务可以使用私有或公共地址。

In order for your kubernetes cluster to be able to get an address you will need to be able to manage route53 from withtin the cluster, for this task I would recommend to use externalDns.为了让您的 kubernetes 集群能够获取地址,您需要能够从集群内部管理 route53,对于此任务,我建议使用 externalDns。

In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.在更广泛的意义上,ExternalDNS 允许您通过 DNS 提供者不可知的方式通过 Kubernetes 资源动态控制 DNS 记录。

source: ExternalDNS来源:外部DNS

To use Ingress in AWS EKS, you need to deploy a pod of LoadBalancerController.要在 AWS EKS 中使用 Ingress,您需要部署 LoadBalancerController 的 pod。 This pod tracks the ingress creation and once an ingress is created, it creates a matching AWS LoadBalancer, which actually handles routing of the incoming traffic directly to the relevant pods.这个 pod 跟踪入口的创建,一旦创建了入口,它就会创建一个匹配的 AWS LoadBalancer,它实际上处理将传入流量直接路由到相关的 pod。

Also, make sure to include the following annotations in the ingress:此外,请确保在入口中包含以下注释:

 kubernetes.io/ingress.class: alb
 alb.ingress.kubernetes.io/scheme: internet-facing
 alb.ingress.kubernetes.io/target-type: ip

See more details in: https://runkiss.blogspot.com/2021/03/using-ingress-in-aws-eks.html查看更多详细信息: https://runkiss.blogspot.com/2021/03/using-ingress-in-aws-eks.html

This happened with me too that after all the setup, I was not able to see the ingress address.这也发生在我身上,在所有设置之后,我无法看到入口地址。 The best way to debug this issue is to check the logs for the ingress controller.调试此问题的最佳方法是检查入口 controller 的日志。 You can do this by:您可以通过以下方式做到这一点:

  1. Get the Ingress controller po name by using: kubectl get po -n kube-system使用以下命令获取 Ingress controller po 名称:kubectl get po -n kube-system
  2. Check logs for the po using: kubectl logs <po_name> -n kube-system使用以下命令检查 po 的日志:kubectl logs <po_name> -n kube-system

This will point you to the exact issue as to why you are not seeing the address.这将为您指出为什么您没有看到该地址的确切问题。

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

相关问题 AWS EKS Fargate Ingress 没有地址 - AWS EKS Fargate Ingress Has No Address 没有地址的 EKS 入口 - 尝试测试我的 EKS 集群 - EKS Ingress without Address - Trying to test my EKS cluster 用于Kubernetes(AWS EKS)的Traefik入口控制器 - Traefik Ingress Controller for Kubernetes (AWS EKS) 将 AWS Cloudformation 资源转换为 EKS 入口配置? - Translating an AWS Cloudformation resource into an EKS ingress configuration? 如何在 AWS-EKS 中使用 ClusterIP 设置入口 - How to set an ingress with ClusterIP in AWS-EKS kubectl 等待 AWS EKS 上的服务公开在.status.loadBalancer.ingress 字段中报告的 Elastic Load Balancer (ELB) 地址 - kubectl wait for Service on AWS EKS to expose Elastic Load Balancer (ELB) address reported in .status.loadBalancer.ingress field 适用于 EKS 的 AWS ALB(入口控制器)前面的 AWS API 网关 - AWS API Gateway infront of AWS ALB (Ingress Controller) for EKS LetsEncrypt 不通过 AWS EKS 中的 Kubernetes 入口和负载均衡器进行验证 - LetsEncrypt not verifying via Kubernetes ingress and loadbalancer in AWS EKS 将 EKS(AWS kubernetes)上 JHub 的入口流量列入白名单的好方法? - Good way to whitelist ingress traffic for JHub on EKS (AWS kubernetes)? 只有“/”适用于 AWS EKS 中的 NGINX 入口控制器和 ALB - Only the '/' works with NGINX ingress controller and ALB in AWS EKS
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM