backend:
serviceName: kong-proxy
servicePort: 8000
path: /app
Result:
HTTP/1.1 404 Not Found
Date: Thu, 17 Jan 2019 08:48:21 GMT
Content-Length: 21
Content-Type: text/plain; charset=utf-8
Kong-Proxy not expose to world using ClusterIP, created ingressroute with specified hostname, the request forward to backend service like Kong-Proxy
Any change required in my ingress route
I am using haproxy ingress controller not kong ingress controller.
the ingress route works with default namespace, but my service are running in different namespace lets example
all kong services are running in kong namespace, haproxy proxy ingress controller running in ingress namespace.
I created sample ingress route with default namespace
Ingress controller doesn’t know the services running in kong namespace, so i created service to route to kong svc
apiVersion: v1
kind: Service
metadata:
name: kongproxy
namespace: ingress
spec:
type: ExternalName
externalName: kong-proxy.kong.svc.cluster.local
ports:
port: 8000
protocol: TCP
The ingress route working fine as expected , if i remove annotations & path, then the ingress looking in the default namespace not in kong namespace.