[patch] temporarily hardcode AI Service tenant operator resources - #519
Merged
Conversation
boonware
marked this pull request as draft
August 5, 2026 12:04
boonware
marked this pull request as ready for review
August 6, 2026 15:20
mnivedithaa
approved these changes
Aug 7, 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.
Issue
MASAIB-2712
Description
Temporarily hardcode the AI Service tenant operator resource requests and limits until the GitOps pipeline fully supports configuring these values. The operator's current requests are too high and this may potentially block a successful upgrade from AI Service 9.1 to 9.2. Work to make these values configurable is underway in #518
Test Results
Pointed ArgoCD to this branch in a test cluster and confirmed that the operator pod was redeployed with the resource changes