LuChenjing opened a new issue #700: URL: https://github.com/apache/apisix-ingress-controller/issues/700
Using helm to install apisix and apisix-ingress-controller.  apisix version: image apache/apisix:2.7-alpine apisix-ingress-controller: image apache/apisix-ingress-controller:1.1.0 Here is the ApisixRoute manifest yaml: ```yaml apiVersion: apisix.apache.org/v2alpha1 kind: ApisixRoute metadata: name: observer-apisixroute namespace: onest-observer spec: http: - name: prometheus-1 match: paths: - /monitor1/* backend: serviceName: prometheus-monitoring-1 servicePort: 9090 plugins: - name: proxy-rewrite enable: true config: regex_uri: - "^/monitor1/(.*)" - "/$1" - name: prometheus-2 match: paths: - /monitor2/* backend: serviceName: prometheus-monitoring-2 servicePort: 9090 plugins: - name: proxy-rewrite enable: true config: regex_uri: - "^/monitor2/(.*)" - "/$1" - name: grafana-rule match: paths: - /dashboard/* backend: serviceName: grafana-ha-svc servicePort: 3000 plugins: - name: proxy-rewrite enable: true config: regex_uri: - "^/dashboard/(.*)" - "/$1" ``` **Issue1:** After applying the resource only shown URIS: /monitor1/*:  Able to access prometheus1  **Issue2:** Able to accesser by /monitor2/ but shown the page of prometheus1  **Issue3:** After delete ApisixRoute, still able to access the prometheus1    -- 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]
