ailunbolinkenasi opened a new issue, #12907:
URL: https://github.com/apache/apisix/issues/12907

   ### Description
   
   I am currently creating a new ApisixRoute under the sso-env-test namespace, 
which requires the maxkey service from the web-sso namespace. However, after 
the creation is complete, it prompts for "makey.web-sso.svc.cluster.local". How 
can APISIX address this issue of cross-namespace communication
   
   ```yaml
   ---
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixRoute
   metadata:
     name: sso-api-main-route
     namespace: sso-env-test
   spec:
     http:
       - backends:
           - serviceName: makey.web-sso.svc.cluster.local
             servicePort: 8000
             weight: 100
         match:
           hosts:
             - web.sso-test.abc.com
           paths:
             - /api
             - /api/*
         name: main-api-route
         plugins:
           - config:
               regex_uri:
                 - ^/api(/.*)?
                 - $1
             enable: true
             name: proxy-rewrite
   status:
     conditions:
       - message: service "makey.web-sso.svc.cluster.local" not found
         observedGeneration: 2
         reason: ResourceSyncAborted
         status: 'False'
         type: ResourcesAvailable
   ````
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to