APM SaaS - UMA agent deployed on Azure opening external IP addresses
Article ID: 216899
Updated On:
Products
Issue/Introduction
We have deployed an UMA agent on AKS and it works fine but we have seen that the agent is trying to open an external IP address and we need to avoid it, is there a way to disable it?
Environment
UMA agent 21.1.0.25
Amazon AKS
Cause
This is coming from the Opentracing extension and it is working as designed
Resolution
It is not a mandate that "opentracing" service needs to have an external ip. The external ip has been made available in case the user wants to ingest opentracing data (zipkin/jaeger) into APM from outside the cluster. If the user is not using it, the "load balancer" part can be disabled and make the service just as a clusterip service , accessible local to the cluster.
This can be done by changing the service definition as below (right side one in the table) in the ca-uma-agent.yaml (Source: uma/templates/deployment_apmia.yaml):
Feedback
