Azure AD Workload Identity uses Kubernetes primitives to associate managed identities for Azure resources and identities in Azure Active Directory (AAD) with pods.
I see that there is Prometheus metrics available on port 8095, however the example in the document/helm chart shows port-forwarding to the deployment to access.
Looking at the service it does not map to 8095--so not sure how the metrics port is supposed to be exposed to Prometheus without changing the existing service to include 8095. Doesn't look like it's configurable through the helm chart.
I see that there is Prometheus metrics available on port 8095, however the example in the document/helm chart shows port-forwarding to the deployment to access.
Looking at the service it does not map to 8095--so not sure how the metrics port is supposed to be exposed to Prometheus without changing the existing service to include 8095. Doesn't look like it's configurable through the helm chart.
Maybe I'm missing something?