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

Namespace is reconfigured when the KedaController is refreshed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.12.z
    • Pod Autoscaler
    • Moderate
    • No
    • 3
    • False
    • Hide

      None

      Show
      None
    • Hide
      Any annotation or label changes to objects managed by Custom Metrics Autoscaler would be reverted by Custom Metrics Autoscaler Operator. This caused continuous changing of labels back and forth when other controllers were used to install Custom Metrics Autoscaler. Custom Metrics Autoscaler now uses its own annotation to know which labels and annotations it is managing and ignores other values.
      Show
      Any annotation or label changes to objects managed by Custom Metrics Autoscaler would be reverted by Custom Metrics Autoscaler Operator. This caused continuous changing of labels back and forth when other controllers were used to install Custom Metrics Autoscaler. Custom Metrics Autoscaler now uses its own annotation to know which labels and annotations it is managing and ignores other values.
    • Bug Fix
    • Proposed

      Description of problem:

      After the operator is installed, the namespace is created with default parameters. Any change done on the namespace, like labelling it, is reverted anytime the KedaController is refreshed (after a config change for example)

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

      v2.10.1

      How reproducible:

      1. Label the openshift-keda namespace
2. Refresh KedaCOntroller

      Actual results:

      Namespace config and labelling is reverted

      Expected results:

      Namespace config and labelling is NOT reverted

              joelsmith.redhat Joel Smith
              rhn-support-rauferna Raul Fernandez (Inactive)
              Weinan Liu Weinan Liu
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: