[patch] include mas_use_service_mesh install parameter to the install pipeline#301
Merged
Conversation
IanBoden
approved these changes
Apr 22, 2026
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.
Description
the mas_use_service_mesh parameter is required by the suite_install role to set istio annotation on the mas core namespace, causing mas core pods to start with the Service Mesh sidecar containers.
Related Issues
https://jsw.ibm.com/browse/MASCORE-12032
Test Results
Developed and tested on the servicemesh-489 cluster. Pre-release testing in personal FVT cluster pds.
FVT test results are here: https://dashboard.ibmmas.com/tests/pds build 6066.
FVT tests show some failures, but similar to normal fvt stable runs, it looks like nothing fundamental is broken by using service mesh: