Looking to see if anyone else is seeing this issue. Seems like leveraging the quick start, config/manifests/metallb-native.yaml deployment the speaker pods do not start. The error reported is "error: open /etc/metallb/excludel2.yaml. permission denied. When i set the runAs user to match the setup for the controller, it gets past this error but I then see issues related to ARP responder for "interface": listen packet XXXXX. socket: operation not permitted. RHEL7, SELinux disabled, firewall off. Was looking to simply test this product out as I see it used quite a bit, however the quick start didnt get it done. Thanks Ron