juzhiyuan opened a new issue, #1142:
URL: https://github.com/apache/apisix-ingress-controller/issues/1142

   ### Issue description
   
   Hi, I followed the document to install APISIX Ingress Controller on GKE. 
However, when I tried this tutorial[1], it showed that "It's not allowed to 
refer to other namespace's service," but I could access other namespace's 
service successfully.
   
   
![image](https://user-images.githubusercontent.com/2106987/177912466-5b2d11ef-5319-42d0-ab3c-1c1694fd8613.png)
   
   [1] 
https://apisix.apache.org/docs/ingress-controller/tutorials/proxy-the-httpbin-service
   
   ### Environment
   
   - your apisix-ingress-controller version (output of 
apisix-ingress-controller version --long): None
   - your Kubernetes cluster version (output of kubectl version): None
   - if you run apisix-ingress-controller in Bare-metal environment, also show 
your OS version (uname -a): None
   
   
   ### Minimal test code / Steps to reproduce
   
   1. Install APISIX Ingress Controller via Helm on GKE, according to 
https://apisix.apache.org/docs/ingress-controller/deployments/gke/. Note: this 
is in the `ingress-apisix` namespace.
   2. Follow this tutorial[1] to run a httpbin pod and apply the 
`httpbin-route.yaml` in the `default` namespace.
   3. Access LoadBalancer's External IP, succeed in accessing the `default` 
namespace's service.
   
   [1] 
https://apisix.apache.org/docs/ingress-controller/tutorials/proxy-the-httpbin-service
   
   ### Actual result
   
   See Steps to reproduce.
   
   ### Error log
   
   None
   
   ### Expected result
   
   
![image](https://user-images.githubusercontent.com/2106987/177913113-1a236f3f-1cef-4fa9-b8ee-2496936690e7.png)
   


-- 
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