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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
I have deployed solo-io_istio-distro via EKS addon. I want to collector Istio tracing data by ADOT. But I am not able to configure the zipkin address in istio-system/istio configmap by EKS addon advance configuration. Since this parameter is not available in the schema.
Below is the config item to be updated in istio-system/istio configmap.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Be able to configure zipkin address in EKS addon advance configuration. Otherwise I have to update the configmap directly. This can be overwritten if I upgrade my addon next time.
Are you currently working around this issue?
I updated the istio-system/istio configmap inside the Kubernetes cluster directly.
Additional context
No
Attachments
No
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
I have deployed solo-io_istio-distro via EKS addon. I want to collector Istio tracing data by ADOT. But I am not able to configure the zipkin address in istio-system/istio configmap by EKS addon advance configuration. Since this parameter is not available in the schema.
Below is the config item to be updated in istio-system/istio configmap.
data.defaultConfig.tracing.zipkin.address
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Be able to configure zipkin address in EKS addon advance configuration. Otherwise I have to update the configmap directly. This can be overwritten if I upgrade my addon next time.
Are you currently working around this issue?
I updated the istio-system/istio configmap inside the Kubernetes cluster directly.
Additional context
No
Attachments
No
The text was updated successfully, but these errors were encountered: