Deconfigure istio proxy tracer explicit to avoid DNS lookups #17811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Debugging a kyma cluster using tcpdump on a privileged pod reveals that constantly DNS lookups for
zipkin.istio-system
are performed. Analyzing the configuration further revealed that the extensionProvider configuration mechanism seems to enable the zipkin tracer additionally to the configured providers. An upstream ticket got created for now istio/istio#45890, we still need to see if we can contribute a fix.As the main problem is the additional stress to CoreDNS with negative DNS lookups, this PR disabled explicitly the tracer in the proxy config as described as a workaround in the upstream bug report.
To validate that the change will not cause any additional DNS entries, deploy a privileged pod (for example using the Gardener terminal) and execute
tcpdump -i any -vvv -s0 -w capture.pcap
.Then copy the captured file using
and analyze the file using wireshark. Enter "dns" as the filter criteria.
Changes proposed in this pull request:
Related issue(s)
istio/istio#45890