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

   ### Description
   
   The apisix has been installed via helm.
   helm repo add apisix https://charts.apiseven.com
   helm repo add bitnami https://charts.bitnami.com/bitnami
   helm repo update
   ADMIN_API_VERSION=v3
   helm install apisix apisix/apisix \
     --set service.type=NodePort \
     --set ingress-controller.enabled=true \
     --create-namespace \
     --namespace ingress-apisix \
     --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix \
     --set ingress-controller.config.apisix.adminAPIVersion=$ADMIN_API_VERSION
     --set ingress-controller.config.kubernetes.enableGatewayAPI=true
   kubectl get service --namespace ingress-apisix
   helm install apisix-dashboard apisix/apisix-dashboard --namespace 
ingress-apisix
   
   export POD_NAME=$(kubectl get pods --namespace ingress-apisix -l 
"app.kubernetes.io/name=apisix-dashboard,app.kubernetes.io/instance=apisix-dashboard"
 -o jsonpath="{.items[0].metadata.name}")
     export CONTAINER_PORT=$(kubectl get pod --namespace ingress-apisix 
$POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")
     echo "Visit http://127.0.0.1:8080 to use your application"
     kubectl --namespace ingress-apisix port-forward $POD_NAME 
8080:$CONTAINER_PORT
   
   I'm trying to routing kubernetes dashboard to a path.
   
   The kubernetes-dashboard service
   
![image](https://github.com/apache/apisix/assets/44300879/3e1d7900-7597-4c91-85e2-1546f078d78c)
   
   The apisix upstream configuration:
   ```json
   {
     "timeout": {
       "connect": 6,
       "send": 6,
       "read": 6
     },
     "type": "roundrobin",
     "scheme": "http",
     "discovery_type": "kubernetes",
     "pass_host": "pass",
     "name": "k8s-dashboard",
     "desc": "from: kubernetes-dashboard/kubernetes-dashboard",
     "service_name": "kubernetes-dashboard/kubernetes-dashboard",
     "keepalive_pool": {
       "idle_timeout": 60,
       "requests": 1000,
       "size": 320
     }
   }
   ```
   
   The apisix route configuration:
   ```json
   {
     "uri": "/k8s",
     "name": "k8s-dashboard",
     "methods": [
       "GET",
       "POST",
       "PUT",
       "DELETE",
       "PATCH",
       "HEAD",
       "OPTIONS",
       "CONNECT",
       "TRACE",
       "PURGE"
     ],
     "upstream_id": "515546170500580115",
     "status": 1
   }
   ```
   
   I also port-forward apisix-gateway: `kubectl port-forward 
service/apisix-gateway 10086:80 -n ingress-apisix  `
   
   Then, when I try to curl it: `curl http://127.0.0.1:10086/k8s`
   It returns:
   ```html
   <html>
   <head><title>503 Service Temporarily Unavailable</title></head>
   <body>
   <center><h1>503 Service Temporarily Unavailable</h1></center>
   <hr><center>openresty</center>
   <p><em>Powered by <a 
href="https://apisix.apache.org/";>APISIX</a>.</em></p></body>
   </html>
   ```
   I don't exactly know what goes wrong.
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   ```
   NAME                                    CHART VERSION   APP VERSION     
DESCRIPTION                                       
   apisix/apisix                           2.7.0           3.9.1           A 
Helm chart for Apache APISIX v3                 
   apisix/apisix-dashboard                 0.8.2           3.0.0           A 
Helm chart for Apache APISIX Dashboard          
   apisix/apisix-ingress-controller        0.14.0          1.8.0           
Apache APISIX Ingress Controller for Kubernetes   
   bitnami/apisix                          3.1.1           3.9.1           
Apache APISIX is high-performance, real-time AP...
   ```
   - Operating system (run `uname -a`): Ubuntu 20.04
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): 1.18.1


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