Clarify change to port names in v6.10.0#1411
Merged
marcleblanc2 merged 2 commits intomainfrom Nov 12, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
jdorfman
reviewed
Nov 12, 2025
Member
jdorfman
left a comment
There was a problem hiding this comment.
I would add "upgrading to" and remove the the comma after "Envoy filter and try again,"
Clarified the update regarding port names and service meshes in Kubernetes, adding additional instructions for users of Istio and Envoy filters.
Clarified instructions regarding Envoy filter removal after upgrading to v6.10.
6534989 to
64f9307
Compare
jdorfman
approved these changes
Nov 12, 2025
This file contains hidden or 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
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.
Clarified the update regarding port names and service meshes in Kubernetes, adding additional instructions for users of Istio and Envoy filters.
Pull Request approval
You will need to get your PR approved by at least one member of the Sourcegraph team. For reviews of docs formatting, styles, and component usage, please tag the docs team via the #docs Slack channel.