You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want the ability to change the port name in spec.ports.name for the Jaeger services (query and collector). This is to allow for custom port names such as http-admin or other names which help enforce HTTPS via Istio. Renaming the port with the prefix http allows Istio to automatically apply mTLS, providing HTTPS for service monitoring.
Problem
I am trying to enable mTLS for service monitors with Prometheus using Istio. The current Jaeger Helm chart does not allow changing the port name in the service monitor configuration, which prevents me from enforcing HTTPS.
I had to manually create service monitors and disable the ones provided by the Helm chart as they don't allow specifying tlsConfig for the Jaeger query and collector service monitors. Here are the links to the current implementations:
The problem arises with the port name. Using the default port name admin results in an unexpected EOF error. However, if I manually change the port name to http-admin in both the service monitor and the service definitions for the Jaeger query and collector, it works correctly with Istio enforcing HTTPS.
Requirement
I want the ability to change the port name in spec.ports.name for the Jaeger services (query and collector). This is to allow for custom port names such as http-admin or other names which help enforce HTTPS via Istio. Renaming the port with the prefix http allows Istio to automatically apply mTLS, providing HTTPS for service monitoring.
Problem
I am trying to enable mTLS for service monitors with Prometheus using Istio. The current Jaeger Helm chart does not allow changing the port name in the service monitor configuration, which prevents me from enforcing HTTPS.
I had to manually create service monitors and disable the ones provided by the Helm chart as they don't allow specifying tlsConfig for the Jaeger query and collector service monitors. Here are the links to the current implementations:
Jaeger query service monitor
Jaeger collector service monitor
My current service monitor specification looks like this:
The problem arises with the port name. Using the default port name admin results in an unexpected EOF error. However, if I manually change the port name to http-admin in both the service monitor and the service definitions for the Jaeger query and collector, it works correctly with Istio enforcing HTTPS.
Proposal
Query Service:
Collector Service:
Open questions
No response
The text was updated successfully, but these errors were encountered: