Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10530

augment location REST API (dynamic bind URIs, normalization "source" prefix)

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • model-registry-bridge
    • None
    • DEVAI Sprint 3277

      Task Description (Required)

      the current POC has "model_name/model_version/content" ; it also creates a unique gin gonic IRoute

       

      Adding an indicator of the source of the normalization,  i.e. was it only based on kserve, or only based on kubeflow, i.e.

      "kubeflow/model_name/model_version/content" or

      "kserve/namespace/name/content" or

      "kubeflow+kserve/model_name/model_version/content"

      will be informative for platform admins, and possibly even app dev's using RHDH.

       

      Then, if we employ bind URL https://gin-gonic.com/docs/examples/bind-uri/  we can create one route handler for each of the model/version tuples.

      See https://github.com/redhat-ai-dev/model-catalog-bridge/pull/6#discussion_r1987947852 for the discussion around pivoting to this, and moving off of the

      current workaround when we explicitly create a new IRoute for each model/version tuple

       

      Note: The scope of this issue only covers Kubeflow as an initial starting point

              gmontero@redhat.com Gabe Montero
              gmontero@redhat.com Gabe Montero
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: