move model-mesh to opendatahub/manifests

[VedantMahabaleshwarkar]

Description

• copied over the latest model-mesh manifests from odh-manifests/model-mesh/odh-modelmesh-controller and put them in opendatahub/manifests along with nessary changes to work with the new directory structure
• separated out modelmesh manifests from odh-model-controller manifests to enable the opendatahub-operator fetching manifests from each individual repo

Testing

The testing for this PR is to be done along with the testing for this and this PR since they target the same set of overall changes.
The ODH operator image has been built with the following changes :

• odh-model-controller manifests are pre built from https://github.com/opendatahub-io/odh-model-controller/tree/manifests_operator_v2 which has equivalent changes to this repo, except that it deploys the image quay.io/vedantm/odh-model-controller:remove-kserve-flag which contains the changes for this PR.
• model-mesh manifests are pre built from https://github.com/opendatahub-io/modelmesh-serving/tree/manifests_transition_v2 and the manfest location is opendatahub/manifests. These manifests are now no longer bundled with odh-model-controller manifests
• opendatahub-operator reconciliation for kserve and modelmesh allow a common deployment of odh-model-controller

How Has This Been Tested?

ModelMesh testing

• cluster login
• git clone git@github.com:VedantMahabaleshwarkar/opendatahub-operator.git
• cd opendatahub-operator
• switch to branch manifests_transition_mlserving
• make deploy -e IMG=quay.io/vedantm/opendatahub-operator:latest
• This will install the ODH operator in NS opendatahub-operator-system with the image quay.io/vedantm/opendatahub-operator:latest
• create the following DSC in NS opendatahub

apiVersion: datasciencecluster.opendatahub.io/v1
kind: DataScienceCluster
metadata:
  name: example
spec:
  components:
    modelmeshserving:
      managementState: Managed

• deploy and test a model with modelmesh

Kserve testing

Note: Cleanup kserve CRDs before testing modelmesh

• cluster login
• install ODH Kserve + dependencies stack by following instructions

Note: Only install the dependencies, the ODH operator will be a custom install according to next steps

• git clone git@github.com:VedantMahabaleshwarkar/opendatahub-operator.git
• cd opendatahub-operator
• switch to branch manifests_transition_mlserving
• make deploy -e IMG=quay.io/vedantm/opendatahub-operator:latest
• This will install the ODH operator in NS opendatahub-operator-system with the image quay.io/vedantm/opendatahub-operator:latest
• create the following DSC in NS opendatahub

apiVersion: datasciencecluster.opendatahub.io/v1
kind: DataScienceCluster
metadata:
  name: default
spec:
  components:
    kserve:
      managementState: Managed

• deploy and test a kserve model using instructions

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: VedantMahabaleshwarkar

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [VedantMahabaleshwarkar]

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

[vaibhavjainwiz]

@VedantMahabaleshwarkar Rather them maintaining manifest in opendatahub/manifests folder could we simply maintain them inside /config folder itself so that it would be more allign with the way we are maintaing manifest for odh-model-controller and kserve.

[VedantMahabaleshwarkar]

replaced by #237