You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/10/17 05:59:47 UTC

[GitHub] [apisix-ingress-controller] shareinto commented on issue #1374: feat: support k8s native ingress and backend service in the different namespace

shareinto commented on issue #1374:
URL: https://github.com/apache/apisix-ingress-controller/issues/1374#issuecomment-1280328849

   Yes, I can understand your doubts, our business sometimes requires ingress and service to be in different namespaces, which depends on the choice of our customers. We found some implementations of the same:
   (1) https://github.com/nginxinc/kubernetes-ingress/tree/v2.3.0/examples/custom-resources/cross-namespace-configuration
   (2) type of externalName service in nginx ingress controller


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org