Thanks @hbagdi!
That looks good! I’m staying with Kong-ingress.
I’m asking that in a context of More control with Kong ACLs
At the moment I’ve got all my Services, Routes and Upstreams generated from Kubernetes Ingress resources. The same resources I’m using for Openshift Router and/or Nginx Ingress configuration.
But as long as we’ve got more complicated requirements on API filtering and restrictions, I see I need to create much more Kubernetes Ingress resources, e.g:
/p1/p2/p3/
/p1/p2/
/p1/
and so forth…
Did I get it right?
Thanks!