Uploaded image for project: 'Open Data Hub'
  1. Open Data Hub
  2. ODH-359

Implement namespace denylist for KfDef deployment

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • operator
    • None

      Certain OCP namespaces that are created by default during normal OCP cluster installation can cause issues when an ODH KfDef uses them as a target namespace for deployment. We need a denylist for namespaces where we prevent deployment of components and provide a KfDef status that deployment is blocked within the namespace

      OCP Namespaces we should target for blocking ODH component deployment

      • default - This causes known issues with PVC creation
      • openshift-operators - There are issues due to the odh-common namespace blindly deploying an OperatorGroup even though one already exists

       

      The **.status message could consist of: 

      Deploying into these namespaces can create failures in ODH components and issues with OpenShift services
      

       

              llasmith@redhat.com Landon LaSmith
              llasmith@redhat.com Landon LaSmith
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: