old_issues_repo
old_issues_repo copied to clipboard
make tracing endpoint configuration straightforward
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:
- 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.
peers
@jsenon
made a fix for it here. If any can review
maybe I should reopen this issue in istio/istio ?