Description of problem: The standalone knmstate operator deploys two instances of webhook pod Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install SNO cluster 2. Install KNMState operator 3. Actual results: two instances of webhook pod Expected results: one instance of webhook pod Additional info:
Verified with kubernetes-nmstate-operator.4.11.0-202205250927 1. Deploy the sno cluster 2. Install KNMState 3. Check the pods [root@ocp-edge39 ~]# oc get pods NAME READY STATUS RESTARTS AGE nmstate-cert-manager-7ff9955f99-kkbnx 1/1 Running 0 53s nmstate-handler-rc9xc 1/1 Running 0 54s nmstate-operator-67744d4779-7kkmv 1/1 Running 0 87s nmstate-webhook-66b4f6bd6-v6wmk 1/1 Running 0 53s Result: Only one instance of webhook pod is created, all pods are OK Additional update case: 1. Deploy the sno cluster 2. Install KNMState 4.11 (not latest) 3. Check the pods (one instance of webhook pod) 4. Update the KNMState to the latest 5. Check the pods (one instance of webhook pod, all pods are OK) Additional upgrade case: 1. Deploy the sno cluster 2. Install KNMState 4.10 3. Check the pods (two instances of webhook pod) 4. Upgrade the KNMState to 4.11 5. Check the pods (one instance of webhook pod, all pods are OK)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069