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

Kserve component should handle wildcard domain

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • No
    • No
    • Moderate
    • Testable
    • Red Hat OpenShift AI

      When setting a domain in the Kserve component, it is expected that the "domain" value is "subdomain.example.com" or similar. When customers supply a wildcard domain, this does not work as expected:

      apiVersion: datasciencecluster.opendatahub.io/v1
      kind: DataScienceCluster
      metadata:
        name: default-dsc
      spec:
        components:
          ...
          kserve:
            serving:
              ingressGateway:
                certificate:
                  secretName: example-wildcard-certificate
                  type: Provided
                domain: '*.subdomain.cloud.example.com'
              managementState: Managed
              name: knative-serving

      The root cause is likely because the Operator is prepending "*." here: https://github.com/opendatahub-io/opendatahub-operator/blob/incubation/pkg/feature/serverless/loaders.go#L32

      The expected format should either be documented or this case should be handled by the Operator.

      Version-Release number of selected component (if applicable):

      rhods-operator.2.7.0
      OpenShift Container Platform 4.13.17

      How reproducible:

      Always

            Unassigned Unassigned
            rhn-support-skrenger Simon Krenger
            RHOAI Model Server and Serving Metrics
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: