sanhofman opened a new issue, #1232: URL: https://github.com/apache/apisix-ingress-controller/issues/1232
### Issue description While deploying APISIX on AWS using apisix-ingress-controller like described here: https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/deployments/aws.md. We get following services up and running: ``` NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE apisix-admin ClusterIP 10.100.219.157 <none> 9180/TCP 5d23h apisix-dashboard ClusterIP 10.100.108.89 <none> 80/TCP 5d18h apisix-etcd ClusterIP 10.100.177.65 <none> 2379/TCP,2380/TCP 5d23h apisix-etcd-headless ClusterIP None <none> 2379/TCP,2380/TCP 5d23h apisix-gateway LoadBalancer 10.100.214.106 aaa8a45985ee54ef1ac414944f615d20-1510783123.eu-central-1.elb.amazonaws.com 80:30114/TCP 5d23h apisix-ingress-controller ClusterIP 10.100.160.139 <none> 80/TCP 5d23h prometheus-operated ClusterIP None <none> 9090/TCP 5d17h ``` Prometheus seems up and running while accessing through port-forward (http://localhost:8090/metrics). But how do we get the URL which can be used by Grafana to read out Prometheus metrics? It seems not exposed so no external IP/URL? ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4.1 - your Kubernetes cluster version (output of kubectl version): v1.22.10 -- 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]
