istio tracing: remove table of version correspondence #20983
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview links (active after the
|
cswatt
approved these changes
Dec 12, 2023
|
I'm going to go ahead and merge this, as out-of-date information isn't of any use. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do? What is the motivation?
A recent correspondence with a customer over an issue with our Istio tracing integration brought to light that our documentation is outdated.
We have a project planned to rewrite our Istio tracing documentation entirely, but for now I think we can remove unnecessary out-of-date information.
This revision removes a table that related Istio's release version to the corresponding Datadog C++ tracing library release version. That correspondence is no longer relevant, the table was out of date, and the context about environment variables included a broken link.
Our support policy for Istio is "when a new Istio release comes out, we support it." I think it's best to leave that implicit, and avoid customers inferring it from a table about library versions.