kubectl cluster-compare reports deviation if BGPAdvertisement CR contains nodeSelectors field:

Cluster CR: metallb.io/v1beta1_BGPAdvertisement_metallb-system_demo-cluster-adv
Reference File: required/networking/metallb/bgp-advr.yaml
Diff Output: diff -u -N /tmp/MERGED-960753510/metallb-io-v1beta1_bgpadvertisement_metallb-system_demo-cluster-adv /tmp/LIVE-2798375576/metallb-io-v1beta1_bgpadvertisement_metallb-system_demo-cluster-adv
--- /tmp/MERGED-960753510/metallb-io-v1beta1_bgpadvertisement_metallb-system_demo-cluster-adv  2024-12-06 18:17:57.259105221 +0200
+++ /tmp/LIVE-2798375576/metallb-io-v1beta1_bgpadvertisement_metallb-system_demo-cluster-adv   2024-12-06 18:17:57.260105230 +0200
@@ -8,7 +8,9 @@
   aggregationLengthV6: 128
   ipAddressPools:
   - demo-cluster-pool
-  localPref: 100
+  nodeSelectors:
+  - matchLabels:
+      egress-service.k8s.ovn.org/demo-ns-my-svc-1: ""
   peers:
   - my-peer
   - my-peer-ipv6

    100%

    1. Create BGPAdvertisement resource that has nodeSelectors field
    2. Run cluster-compare tool
    3.
    

    Deviation is reported

    Should be tolerated by the tool