[Service Registy] CORS_ALLOWED_ORIGINS is not propagated as env on the resulted pod

Solution Verified - Updated -

Issue

  • CORS_ALLOWED_ORIGINS is not propagated as env on the resulted pod.
    For instance:

    oc get ApicurioRegistry/apicurioregistry-psql -o yaml | grep CORS_ALLOWED_ORIGINS -A2
        - name: CORS_ALLOWED_ORIGINS
          value: https://login.dev.com, https://schema-registry.dev.com
    

    However in the pod, we have the following env:

    oc rsh apicurioregistry-psql-deployment-7db9dd59cb-c24dj env | grep CORS_ALLOWED_ORIGINS
    CORS_ALLOWED_ORIGINS=http://apicurioregistry-psql.sr.router-default.apps,https://apicurioregistry-psql.sr.router-default.apps
    

Environment

  • Red Hat Service Registry: 2.4.3
  • Red Hat OpenShift Container (Openshift) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content