Has anyone managed to solve this problem? I have the same EMPTY_RESPONSE error after testing @Enzos23 solution.
Is there a similar solution for Google Kubernetes Engine? Having the same issue, but can’t use any of those aws annotations.
hi @hbagdi,
I am experience similar issues with kong, Below is my config . i used helm to install the kong ingress controller
type or proxy:
# Enable creating a Kubernetes service for the proxy
enabled: true
type: LoadBalancer
# To specify annotations or labels for the proxy service, add them to the respective
# "annotations" or "labels" dictionaries below.
annotations:
# If terminating TLS at the ELB, the following annotations can be used
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http,
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: true,
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: 3600,
service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy: ELBSecurityPolicy-2016-08,
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:eu-west-1:127867112076:certificate/25044570-f0a1-4220-ba3c-c88f79731137,
service.beta.kubernetes.io/aws-load-balancer-ssl-ports: 443,
service.beta.kubernetes.io/aws-load-balancer-type: elb
labels:
enable-metrics: "true"
http:
# Enable plaintext HTTP listen for the proxy
enabled: true
servicePort: 80
containerPort: 8000
# Set a nodePort which is available if service type is NodePort
# nodePort: 32080
# Additional listen parameters, e.g. "reuseport", "backlog=16384"
parameters: []
tls:
# Enable HTTPS listen for the proxy
enabled: true
servicePort: 443
containerPort: 8443
# Set a target port for the TLS port in proxy service
overrideServiceTargetPort: 8000paste code here
On the Load balancer dashboard the SSL certificate does not reflect
.I added the kong_trusted_ip to the normal env and not customenv
Kindly advice