Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-66

[RFE]Allow some apiserver configuration (spec.additionalCORSAllowedOrigins)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • False
    • Undefined
    • 0
    • 0
    • 0

      The MTC UI relies on configuring additional cors allowed origins in http://config.openshift.io/v1/apiserver/cluster to function.

      oc get apiserver.config.openshift.io/cluster -o go-template='{{ range .spec.additionalCORSAllowedOrigins }}{{ println . }}{{ end }}'
(?i)//migration-openshift-migration\.jmatthews-dal10-b3c-4x16-b848826e1b241c715949ecfb666729c9-0000\.us-south\.containers\.appdomain\.cloud(:|\z)
//127.0.0.1(:|$)
//localhost(:|$)

      In IBM ROKS this configuration currently exists, but does not have the desired effect and I still see CORS errors in the UI, which prevent it from working properly.

        1. image.png
          image.png
          60 kB

            Unassigned Unassigned
            rhn-engineering-jmontleo Jason Montleon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: