Remove ragImage configuration from CR#8
Merged
Conversation
Collaborator
Author
|
Ran kuttl tests locally, it's good: |
Collaborator
|
LGTM, thank you:) |
For tech preview, the RAG images are built with specific requirements (e.g., bundled with OKP embedding model) that are not yet available to customers. Removing the field prevents users from supplying custom RAG images that would lack these dependencies and break things. The operator continues to use the image pinned via the RELATED_IMAGE_OPENSTACK_LIGHTSPEED_IMAGE_URL_DEFAULT environment variable, which is set to a known image at operator build time. Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
Collaborator
|
/lgtm Sorry, I missed this one. |
lpiwowar
approved these changes
Jul 9, 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
4 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.
For tech preview, the RAG images are built with specific requirements (e.g., bundled with OKP embedding model) that are not yet available to customers. Removing the field prevents users from supplying custom RAG images that would lack these dependencies and break things.
The operator continues to use the image pinned via the RELATED_IMAGE_OPENSTACK_LIGHTSPEED_IMAGE_URL_DEFAULT environment variable, which is set to a known image at operator build time.