Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-23976

Namespace keda is created after deploying CMA in openshift-keda

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.14.0
    • Pod Autoscaler
    • None
    • Low
    • No
    • 3
    • PODAUTO - Sprint 256, PODAUTO - Sprint 257
    • 2
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When customers install the CMA in a custom namespace or in the default namespace, a second namespace called "keda" is created. The issue is also described here: https://access.redhat.com/solutions/7046442

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

      New installation of CMA in OpenShift Container Platform 4.13

      How reproducible:

      On customer cluster

      Steps to Reproduce:

          1. Install the Custom Metrics Autoscaler in a custom namespace

      Actual results:

          Custom Metrics Autoscaler is installed in the custom namespace, however "keda" namespace is also created

      Expected results:

           Custom Metrics Autoscaler is installed in the custom namespace, no additional namespace is created

      Additional info:

              joelsmith.redhat Joel Smith
              rhn-support-dgautam Dhruv Gautam
              Aditi Sahay Aditi Sahay
              Votes:
              2 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: