unexpected drift on cluster-bmh unit
The following unexpected resource drift correction happened in a CI job (this is the second time I see it):
❌ Unexpected drift detected in:
🔹 cluster-bmh
Action: Secret/kubeadm-capm3-virt/workload-cp-0-preprovisioning-netdata changed (1 additions, 0 changes, 0 removals)\nSecret/kubeadm-capm3-virt/wc-1782732422-kubeadm-capm3-virt-workload-cp-0-secret excluded\nSecret/kubeadm-capm3-virt/wc-1782732422-kubeadm-capm3-virt-workload-cp-1-secret excluded\nSecret/kubeadm-capm3-virt/wc-1782732422-kubeadm-capm3-virt-workload-cp-2-secret excluded\nSecret/kubeadm-capm3-virt/wc-1782732422-kubeadm-capm3-virt-workload-md-0-secret excluded","type":"Warning","object":{"kind":"HelmRelease","namespace":"kubeadm-capm3-virt","name":"cluster-bmh","uid":"0c71ddf2-b51b-480e-a6a2-51421322f292","apiVersion":"helm.toolkit.fluxcd.io/v2","resourceVersion":"59752"},"reason":"DriftDetected}https://gitlab.com/sylva-projects/sylva-core/-/jobs/9806770062
We need to investigate why the cluster-bmh unit would be subject to such a drift.