diff --git a/Jenkinsfile b/Jenkinsfile
index e3a6443..52e3bb8 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -114,25 +114,11 @@ pipeline {
             steps {
                 withKubeConfig([credentialsId: "${K8S_CRED_ID}"]) {
                     sh """
-                        # Install MetalLB if not already present (idempotent)
-                        kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.14.8/config/manifests/metallb-native.yaml
-
-                        # Controller must be ready before applying CRDs
-                        kubectl rollout status deployment/controller -n metallb-system --timeout=120s
-
-                        # Speaker runs on every node as a DaemonSet.
-                        # On CPU-constrained clusters it may be slow — don't fail the
-                        # pipeline, just print status so we can diagnose if needed.
-                        kubectl rollout status daemonset/speaker -n metallb-system --timeout=180s || {
-                            echo "WARNING: MetalLB speaker rollout not complete — printing diagnostics"
-                            kubectl get pods -n metallb-system -o wide
-                            kubectl describe pods -l component=speaker -n metallb-system | grep -A 10 Events
-                        }
-
-                        # Apply IP pool and L2Advertisement (idempotent)
+                        # MetalLB is already installed on this cluster (metallb-speaker-*
+                        # and metallb-controller-* pods). Just apply the IP pool config.
                         kubectl apply -f k8s/overlays/on-premise/metallb/
 
-                        echo "MetalLB setup done. Current pod state:"
+                        echo "MetalLB pod state:"
                         kubectl get pods -n metallb-system -o wide
                     """
                 }