Kong behind CDN #14269
Labels
area/ingress-controller
Issues where Kong is running as a Kubernetes Ingress Controller
area/kubernetes
Issues where Kong is running on top of Kubernetes
Hi,
I am running Kong in my Kubernetes cluster behind a service and a CDN. I have an HTTPRoute with a hostname:
The problem is that I accept traffic to
service-a.example.com
public domain, but my internal hostname isservice-a.private-domain
, but Kong gets theHost
header asservice-a.example.com
and does not match any route.How can I ignore the Host header of my CDN?
The text was updated successfully, but these errors were encountered: