[minor] Invoke AI Service migration from update pipeline#2171
Merged
Conversation
boonware
changed the title
whitfiea
approved these changes
Apr 15, 2026
whitfiea
changed the title
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
3 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.
Issue
MASAIB-1994
Description
Run the AI Service migration role during the MAS update pipeline. This role will be invoked if and only if there are AI Service instances in the cluster. The migration role itself will determine if a migration is necessary and perform the migration steps. A migration may be needed during an update as going from one feature channel release that does not contain the new namespace-scoped tenant operator to a feature channel release that does will require migration; this migration would otherwise be performed during an upgrade from 9.1 to 9.2.
Depends On
Test Results
Tested by installing an earlier 9.2.x feature channel build of AI Service that does not include the new namespace-scoped tenant operator. Then performed an update to a new feature channel release that does include the operator and confirmed that migration was run successfully.