Feature Overview (aka. Goal Summary)

During the 1.10 refinement for https://issues.redhat.com/browse/RHDHPLAN-404 agreement was reached to move out RHDHPLAN-404 to a 1.11 candidate, and create this spike feature to track work during the 1.10 time frame along these lines:

• convert our existing golang code to typescript (AI assisted when appropriate)
• engage with upstream on
  • consensus, similar to what is going on upstream for MCP servers, for representing AI Models/Model Servers in the catalog
  • consensus on where plugins that import Model related metadata reside (core vs. community)
  • confirm guidance on use of the backstage k8s plugin vs. direct use of the k8s typescript library; we also wonder on where a plugin reside may have an impact on this
• engage with RHOAI and kubeflow upstream on
  • are suspicion that key elements of our model catalog -> model registry techdoc dependencies are mistreamed/downstreamed vs. upstreamed 
  • if correct, are there plans to upstream features in this space 

Goals (aka. expected user outcomes)

Have dependencies sufficiently answered so we can deliver and upstream plugin version of the connector in the 1.10 time frame

Requirements (aka. Acceptance Criteria):

• RFC / BEP opened, with in progress review, during 1.10 time frame
• Github branch with a demo'able typescript only plugin that communicates with 
  • RHOAI Model Registry on OCP
  • Upstream Kubeflow/KServe running locally on a laptop running those project directly, or within a local version of k8s i.e. minikube / kind
• Documentation of the k8s plugin findinds
• Documentation of the techdoc req's and where they do (or will in the future) land in the RHOAI upstream/midstream/downstream

High-level list of items that are out of scope.

• actual delivery of a plugin in either core or community upstream is assumed to be untenable by 1.10 feature freeze, and will be carried forward in 1.11 or beyond with RHDHPLAN-404

Customer Considerations (Optional)

Keep an eye to see if any internal or external customer are will to try early POCs

Documentation Considerations

Other than documenting investigation results, and external / user facing doc changes are pushed to RHDHPLAN-404