[release-1.28] Add "ztunnelNamespace" flag to converter flow#635
Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-service-mesh:release-1.28from Mar 5, 2026
Conversation
As follow of this upstream Istio PR work, add the "ztunnelNamespace" flag to the converter flow. istio/istio#58677 Signed-off-by: Maxim Babushkin <mbabushk@redhat.com>
MaxBab
changed the title
FilipB
approved these changes
Mar 5, 2026
openshift-merge-bot
bot
merged commit cab48e9
into
openshift-service-mesh:release-1.28
9 of 10 checks passed
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
2 participants
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.
Please provide a description of this PR:
Manual cherry-pick of #593
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.
Please check any characteristics that apply to this pull request.
Required PR Label: Please add one of the following labels to this PR:
permanent-change: For OSSM-specific changes that should be cherry-picked to release branchesno-permanent-change: For temporary changes that will be removed and should NOT be cherry-pickedThis labeling helps release maintainers identify which changes to include in new release branches.