[英]AWS EKS - Create Load Balancer Service throws out of service
I have a quick question regarding AWS EKS that whenever I create a K8s service with of type LoadBalancer, it provisions a classic ELB backed the EC2 where services are running. 我有一个关于AWS EKS的快速问题,每当我创建一个类型为LoadBalancer的K8s服务时,它就会提供一个经典的ELB支持运行服务的EC2。 Now whenever I try to hit the Load Balancer ELB from the Internet, it returns ERR_EMPTY_RESPONSE error.
现在,每当我尝试从Internet访问Load Balancer ELB时,它都会返回ERR_EMPTY_RESPONSE错误。 If I navigate back to ELB and look at the instances behind ELB, it shows the status of EC2 instances as OutOfService.
如果我导航回ELB并查看ELB背后的实例,它会将EC2实例的状态显示为OutOfService。
This happens either I use my own K8s deployments & services or the one provided with documentation. 发生这种情况要么是我使用自己的K8s部署和服务,要么是使用文档提供的部署和服务。 Anyone can help me with this?
有人可以帮我这个吗? More over, is there any way to provision a different type of Load Balancer for a K8s service?
更重要的是,有没有办法为K8s服务配置不同类型的负载均衡器? Thanks.
谢谢。
This is default behavior or K8S with on cloud providers , A service type Load Balancer will spins up real one which affect cost. 这是默认行为或K8S与云提供商,服务类型负载均衡器将旋转实际影响成本。 Better to use K8S Ingress as best practice and can use as Endpoint or you can add under External Load Balancer.
最好使用K8S Ingress作为最佳实践,并可以用作Endpoint,或者可以在External Load Balancer下添加。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.