Task

As an engineer working on RHDH, I want to demonstrate the typescript only connector against upstream kserve

Background

• Instructions for running the upstream version of kserve on minikube are over at https://kserve.github.io/website/docs/developer-guide 
• Stretch related:  using Kserve with Kubeflow, including reference to a web interface, are over at https://www.kubeflow.org/docs/components/kserve/introduction/#how-to-use-kserve-with-kubeflow 
•  

Dependencies and Blockers

No QE or Doc dependencies 

Acceptance Criteria

Using the output from RHIDP-11757, stand up upstream versions of the registry, catalog, and if possible UI, and demonstrate population of the registry that leads the importing of that content into the backstage catalog as Resources when the typescript only form of the connector is integrated with the upstream registry/catalog.

Make updates as needed to the connector to work with upstream vs. RHOAI/ODH

STRETCH:  after validating vanilla, standalone, kserve, if possible, see how much of the kubeflow/kserve integration from https://www.kubeflow.org/docs/components/kserve/introduction/#how-to-use-kserve-with-kubeflow you can get working, and then see what happens when you point our connector to it