Is it possible to establish an ingress rule via kong-ingress-controller without a separate nginx-ingress-controller in the k8s cluster and without NodePorts?
The k8s cluster is established via Rancher.
Rancher automatically deploys a nginx-ingress-controller. If I am deploying a service and the related ingress rule, the service is accessible from outside the k8s cluster without NodePorts, just with the IP Address + defined path as URI.
Now i expect that the behaviour of the kong-ingress-controller is the same like nginx-ingress-controller. So I deinstalled the nginx controller and want to use just the kong controller. But if I am deploying the same ingress rule it is not accessible from outside, just with IP:NodePort/path.
So first question: Is it possible to only use kong-ingress-controller without any other controller?
Second question: How can i mange it, that the behaviour is the same like described in “current state”?