Description of problem:
The etcd-operator is unnecessarily triggering reconciliation in response to any configmap watch event across all namespaces. Given the volume and churn of configmaps in any nontrivial production cluster, combined with the actions performed during a reconciliation (which at present include active etcd API calls to list members and their status), the resulting chatter with etcd seems excessive (although I haven't yet performed systematic measurements).
Version-Release number of selected component (if applicable):
Launch a new cluster IPI cluster on any platform.
The etcd-operator reconciles once for every configmap in the system, and then in response to any change to any configmap in the system after the initial sync.
The etcd-operator should only reconcile when relevant changes (e.g. node churn) occur.
Tried with 4.5.0-0.nightly-2020-05-19-041951, the map trend looks like well, pls comments if any misunderstanding.
*** Bug 1812718 has been marked as a duplicate of this bug. ***
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.