istio/old_issues_repo

make tracing endpoint configuration straightforward

Opened this issue · 2 comments

visheyra commented

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:

  1. Update the istio configuration in the istio configmap
  • kind: ConfigMap
  • name: istio
  • namespace: istio-system
  1. Update the mixer deployment and change a command line argument
  • Kind: Deployment
  • Name: istio-mixer
  • Namespace: istio-system
  • cli arg: trace-zipkin-url
  1. 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

visheyra commented

made a fix for it here. If any can review

visheyra commented

maybe I should reopen this issue in istio/istio ?