[英]After adding AWS ACM EKS ELB is not opening on HTTPS
I have my app running on EKS which is using istio-ingressgateway service for load balancer and Knative serving I have added ACM to my ELB, but after patching the service with我在 EKS 上运行我的应用程序,它使用 istio-ingressgateway 服务进行负载均衡器和 Knative 服务我已将 ACM 添加到我的 ELB,但在修补服务后
metadata:
annotations:
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: "arn:aws:acm:xx-xxxx-1:1234567890:certificate/xxxxxx-xxx-dddd-xxxx-xxxxxxxx"
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
my domain is not opening on HTTPS but works fine on HTTP giving this error on HTTPS我的域没有在 HTTPS 上打开,但在 HTTP 上工作正常,在 HTTPS 上出现此错误
< HTTP/1.1 408 REQUEST_TIMEOUT
HTTP/1.1 408 REQUEST_TIMEOUT
< Content-Length:0
Content-Length:0
< Connection: Close
Connection: Close
Hope you your load balancer forward the traffic from 443 to the backend target port 3190 in case of Istio.希望您的负载均衡器在 Istio 的情况下将流量从 443 转发到后端目标端口 3190。 Check your Istio gateway file wether you have 443 port mapped with the targets.
检查您的 Istio 网关文件,您是否已将 443 端口映射到目标。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.