Uploaded image for project: 'Zero Trust Workload Identity Manager'
  1. Zero Trust Workload Identity Manager
  2. SPIRE-246

ConfigMap Labels Not Restored During Reconciliation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Critical

      ConfigMap labels removed manually are NOT automatically restored by the operator during reconciliation, indicating that PR #51's label reconciliation fix does not apply to ConfigMaps.

       

      cmd to find labels: 

      oc get configmap spire-server -n $NAMESPACE -o yaml | grep -A 10 "labels:"

      OP => 

      labels:
          app.kubernetes.io/component: control-plane
          app.kubernetes.io/instance: cluster-zero-trust-workload-identity-manager
          app.kubernetes.io/managed-by: zero-trust-workload-identity-manager
          app.kubernetes.io/name: spire-server
          app.kubernetes.io/part-of: zero-trust-workload-identity-manager
          app.kubernetes.io/version: 1.12.4
        name: spire-server
        namespace: zero-trust-workload-identity-manager
        ownerReferences:
        - apiVersion: operator.openshift.io/v1alpha1

       

      Removing   app.kubernetes.io/managed-by: zero-trust-workload-identity-manager  labels => 

      cmd =>  

      oc label configmap spire-server -n zero-trust-workload-identity-manager app.kubernetes.io/managed-by-

      expected behavior:

      The operator should detect the missing label during reconciliation and automatically restore it:

      labels:
        app.kubernetes.io/managed-by: zero-trust-workload-identity-manager  # ← Should be restored 

       

      Actual :

      Actual Behavior
      Label remains missing after reconciliation
      resourceVersion does not change
      Operator does not update the ConfigMap

       

              rh-ee-aagnihot Anirudh Agnihotri
              rh-ee-sayadas SAYAK DAS
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: