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
{{ message }}
This repository has been archived by the owner on Feb 16, 2019. It is now read-only.
It would be nice if one could simply configure the zipkin endpoint in the different component that needs it.
Use case
I want to change my jaeger instance namespace (let's say tracing instead of istio-system)
Current "working so far" alternatives
The good one
I have to do the following operations:
Update the istio configuration in the istio configmap
kind: ConfigMap
name: istio
namespace: istio-system
Update the mixer deployment and change a command line argument
Kind: Deployment
Name: istio-mixer
Namespace: istio-system
cli arg: trace-zipkin-url
Update the ingress deployment and change a command line argument
Kind: Deployment
Name: istio-ingress
Namespace: istio-system
cli arg: zipkinAddress
The bad one
One could make a dirty fix by adding an externalName in the istio-system namespace and make it point to jaegertracing.<YOUR_NS>.svc.cluster.local. I think this dirty fix would not work with mTLS enabled.
thoughts
Since this configuration is not available in the helm chart, doing it manually with the above methods are the only that would works.
Is this a BUG or FEATURE REQUEST?:
Feature Request:
Yes
Describe the feature:
It would be nice if one could simply configure the zipkin endpoint in the different component that needs it.
Use case
I want to change my jaeger instance namespace (let's say tracing instead of istio-system)
Current "working so far" alternatives
The good one
I have to do the following operations:
The bad one
One could make a dirty fix by adding an externalName in the istio-system namespace and make it point to
jaegertracing.<YOUR_NS>.svc.cluster.local
. I think this dirty fix would not work with mTLS enabled.thoughts
Since this configuration is not available in the helm chart, doing it manually with the above methods are the only that would works.
peers
@jsenon
The text was updated successfully, but these errors were encountered: