Open mkyc opened 1 year ago
You can expose the control api outside, with assigning its ip address to 0.0.0.0 (in the config.yaml). But it's not supported by helm chart, we may need to extend the helm chart first.
Ok, I get it. AFAICT I'd need to add some k8s Service
as well, separately from helm chart. Because of this documentation line I guess it would make sense to introduce some controlAPI.expose
(or anything like that) helm chart parameter. Otherwise one needs to move whole config.yaml
to values.yaml
variable, which is not super convenient.
I believe the Helm Chart still does not support exposing the Control API, but it's enabled by default, right?
I want to be able to monitor APISIX gateway deployment instance from my AWS ALB load balancer. I just want to monitor that gateway instance is UP, and not focus on specific routes. It looks to me that
server-info
plugin is perfect for that. According to documentation I need to access/v1/server_info
endpoint from ALB. As far as I can tell from helm chart ControlAPI port (9090) is not exposed from pod and there is no corresponding configuration to expose it inapisie-gateway
orapisix-admin
services. Am I correct? Is there any possible workaround?