Closed ruivieira closed 2 months ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yhwang
The full list of commands accepted by this bot can be found here.
PR image build and manifest generation completed successfully!
📦 PR image: quay.io/trustyai/trustyai-service-operator-ci:a97f57cef0a8569883732689434314b27887dfce
📦 Driver image: quay.io/trustyai/ta-lmes-driver:a97f57cef0a8569883732689434314b27887dfce
🗂️ CI manifests
Nice overlays! Just one minor question: In your change, the base is
TAS+LMES
and ODH inherits the base. RHOAI overrides it toTAS
only. The other way around is to keep the base asTAS
only and change ODH toTAS+LMES
, then for RHOAI, it can inherit from the base directly.These two approaches all deliver the same outcome. I guess the key point is: the base should be
TAS
only orTAS + LMES
. This may be also related to how the e2e test deploys the operator. I will leave this to you. I am good with either way.
Thanks @yhwang that's a good point.
Personally, I think we should keep the base as LMES+TAS. ODH can just inherit from base. We then provide LMES only for specific use cases. Any downstream can then configure the controllers in their respective forks. In this case, the overlay for LMES+TAS is in fact redundant.
I will change the GHA to build the ta-lmes-job
in a separate PR.
New changes are detected. LGTM label has been removed.
i am good with this PR, looks neat and only small changes required from Platform when enable this feature.
Add overlays to support selective controller configuration:
odh
andlmes-tas
overlays enable bothTAS
andLMES
rhoai
overlay enablesTAS
only (disablesLMES
)