feat: Add TrustyAI component

[ruivieira]

Description

• This PR adds TrustyAI as a component to the ODH operator.
• This PR targets the incubation branch, rather than main (as feat: Add TrustyAI component #568 did).
• TrustyAI operator manifests are now retrieved from the upstream release/* branches.

How Has This Been Tested?

Tested with sample DSC CR including the new

spec:
  components:
    trustyai:
      managementState: "Managed"

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[ruivieira]

cc @zdtsw @ykaliuta

[zdtsw]

@ruivieira i did a test from your code base
imageParamMap still need update for:
so the idea is it should be in the format of "image_name:image_tag"
take https://github.com/red-hat-data-services/odh-manifests/blob/master/data-science-pipelines-operator/base/params.env as example.
so i would say https://github.com/trustyai-explainability/trustyai-service-operator/blob/release/1.10.1/config/base/params.env will be something like

trustyaiServiceImage=quay.io/trustyai/trustyai-service:v0.5.0
trustyaiOperatorImage=quay.io/trustyai/trustyai-service-operator:v1.10.1

then we do

var imageParamMap = map[string]string{
	"trustyaiServiceImage":  "RELATED_IMAGE_ODH_TRUSTYAI_SERVICE_IMAGE",
	"trustyaiOperatorImage": "RELATED_IMAGE_ODH_TRUSTYAI_OPERATOR_IMAGE",
}

[ruivieira]

@ruivieira i did a test from your code base imageParamMap still need update for: so the idea is it should be in the format of "image_name:image_tag" take https://github.com/red-hat-data-services/odh-manifests/blob/master/data-science-pipelines-operator/base/params.env as example. so i would say https://github.com/trustyai-explainability/trustyai-service-operator/blob/release/1.10.1/config/base/params.env will be something like

trustyaiServiceImage=quay.io/trustyai/trustyai-service:v0.5.0
trustyaiOperatorImage=quay.io/trustyai/trustyai-service-operator:v1.10.1

then we do

var imageParamMap = map[string]string{
	"trustyaiServiceImage":  "RELATED_IMAGE_ODH_TRUSTYAI_SERVICE_IMAGE",
	"trustyaiOperatorImage": "RELATED_IMAGE_ODH_TRUSTYAI_OPERATOR_IMAGE",
}

Thanks @zdtsw. I'll change to env format upstream so it matches the expectation here.

[zdtsw]

@ruivieira i did a test from your code base imageParamMap still need update for: so the idea is it should be in the format of "image_name:image_tag" take https://github.com/red-hat-data-services/odh-manifests/blob/master/data-science-pipelines-operator/base/params.env as example. so i would say https://github.com/trustyai-explainability/trustyai-service-operator/blob/release/1.10.1/config/base/params.env will be something like

trustyaiServiceImage=quay.io/trustyai/trustyai-service:v0.5.0
trustyaiOperatorImage=quay.io/trustyai/trustyai-service-operator:v1.10.1

then we do

var imageParamMap = map[string]string{
	"trustyaiServiceImage":  "RELATED_IMAGE_ODH_TRUSTYAI_SERVICE_IMAGE",
	"trustyaiOperatorImage": "RELATED_IMAGE_ODH_TRUSTYAI_OPERATOR_IMAGE",
}

Thanks @zdtsw. I'll change to env format upstream so it matches the expectation here.

once that is done, i will do a final test and we can get this PR out

[zdtsw]

one more thing @ruivieira could you update https://github.com/opendatahub-io/opendatahub-operator/blob/incubation/components/README.md inthe

[ruivieira]

@zdtsw We had to wait quite a bit for the CI to finish, after the params.env format change, but it's all done now and the new manifests are available at https://github.com/trustyai-explainability/trustyai-service-operator/tree/release/1.10.2 and corresponding images available on quay.io. The README.md was also updated.

[zdtsw]

test on local build, looks good
/lgtm

[zdtsw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: zdtsw
Once this PR has been reviewed and has the lgtm label, please assign vaishnavihire for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment