Uploaded image for project: 'Red Hat OpenShift AI Engineering'
  1. Red Hat OpenShift AI Engineering
  2. RHOAIENG-5322

[ccs] Ability to select private/public routes for endpoints in KServe

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • Documentation
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOAISTRAT-182 - Ability to select private/public routes for endpoints in KServe
    • RHOAISTRAT-182Ability to select private/public routes for endpoints in KServe
    • No
    • No
    • RHOAI DOCS 2.10
    • Testable

      As described in feature issue, RHOAISTRAT-182:

      Currently we are in a situation where KServe endpoints always have a public endpoint and we can not add authentication to them.  The second part of this problem is being addressed by incorporating Authorino into OpenShift AI, but the ability for a customer to choose to have a private endpoint that is unauthenticated will not be solved by this work.  The goal of this feature is to have a way for a customer to choose whether their endpoint will be public or private.

      The default state should be that the endpoint is private once this work is complete.

      Once a model is served it should be possible to change the designation of whether it has a public endpoint or not.

      See also the feature refinement doc here.

            jbyrne@redhat.com John Byrne
            jbyrne@redhat.com John Byrne
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: