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

cluster-version-operator no-op reconciling kube-rbac-proxy ConfigMap

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.14, 4.15, 4.16, 4.17, 4.18, 4.19, 4.20
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • No
    • None
    • None
    • In Progress
    • Bug Fix
    • Hide
      The cluster-version operator and machine-config operator used to fight over the presence of a trailing newline in the config-file.yaml data in the kube-rbac-proxy ConfigMap in the openshift-machine-config-operator namespace. That generated unecessary Kubernetes API churn, and possibly other side effects that the MCO folks can talk about. This change removes that contention.
      Show
      The cluster-version operator and machine-config operator used to fight over the presence of a trailing newline in the config-file.yaml data in the kube-rbac-proxy ConfigMap in the openshift-machine-config-operator namespace. That generated unecessary Kubernetes API churn, and possibly other side effects that the MCO folks can talk about. This change removes that contention.
    • None
    • None
    • None
    • None

      Description of problem:

      While debugging why kube-rbac-proxy-crio pods are being re-created, we noticed that CVO is reporting a diff on the kube-rbac-proxy configmap in the openshift-machine-config-operator namespace and that appears to be updating the configmap, triggering a rollout?

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

      Seen on 4.19.17 at least

      How reproducible:

      Very    

      Steps to Reproduce:

          1. Create a 4.19.17 cluster
          2. Look for CVO logs like Updating ConfigMap openshift-machine-config-operator/kube-rbac-proxy due to diff
          3. Notice kube-rbac-proxy-crio pods recreating in openshift-machine-config-operator namespace. Journal logs from kubelet report that the static pod is different than the manifest and thus re-creates it.

      Actual results:

      kube-rbac-proxy-crio pods are churning in the openshift-machine-config-operator namespace    

      Expected results:

          No changes to the configmap exists so CVO shouldn't be patching it

      Additional info:

      I0309 15:41:00.899219       1 core.go:138] Updating ConfigMap openshift-machine-config-operator/kube-rbac-proxy due to diff:   &v1.ConfigMap{
            TypeMeta: v1.TypeMeta{
      -         Kind:       "",
      +         Kind:       "ConfigMap",
      -         APIVersion: "",
      +         APIVersion: "v1",
            },
            ObjectMeta: v1.ObjectMeta{
                ... // 2 identical fields
                Namespace:                  "openshift-machine-config-operator",
                SelfLink:                   "",
      -         UID:                        "04b46684-51aa-41f9-9d83-fc6161807b18",
      +         UID:                        "",
      -         ResourceVersion:            "109522460",
      +         ResourceVersion:            "",
                Generation:                 0,
      -         CreationTimestamp:          v1.Time{Time: s"2025-12-02 01:55:19 +0000 UTC"},
      +         CreationTimestamp:          v1.Time{},
                DeletionTimestamp:          nil,
                DeletionGracePeriodSeconds: nil,
                ... // 2 identical fields
                OwnerReferences: {{APIVersion: "config.openshift.io/v1", Kind: "ClusterVersion", Name: "version", UID: "3a40857a-fc31-447c-9418-a28dfac22a39", ...}},
                Finalizers:      nil,
      -         ManagedFields: []v1.ManagedFieldsEntry{
      -             {
      -                 Manager:    "cluster-version-operator",
      -                 Operation:  "Update",
      -                 APIVersion: "v1",

              trking W. Trevor King
              jbranham.openshift Josh Branham
              Jia Liu Jia Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: