OPNET-303: Remove weights from ingress check script

Previously, because we had weights set for both check scripts for
ingress, keepalived would always assign the ingress VIP somewhere,
even if there were no ingress controllers available. While normally
this is not a problem, this behavior is not ideal in circumstances
such as remote workers where one worker per remote subnet will take
the VIP because they can't coordinate with the other subnets.

The advantage of removing the weight from the check script is that
if there is no ingress controller running on the node it will never
take the VIP, even if no other node in the cluster has taken it.
This allows us to deploy remote workers without the extra step of
disabling keepalived. As long as the ingress pods are deployed to
the correct nodes keepalived will handle assigning the VIP on its
own, even across subnets that can't communicate directly with each
other.

templates/master/00-master/on-prem/files/keepalived-keepalived.yaml

@@ -41,7 +41,6 @@ contents:
     vrrp_script chk_ingress {
         script "/usr/bin/timeout 0.9 /usr/bin/curl -o /dev/null -Lfs http://localhost:1936/healthz/ready"
         interval 1
-        weight 20
         rise 3
         fall 2
     }

templates/worker/00-worker/on-prem/files/keepalived-keepalived.yaml

@@ -14,7 +14,6 @@ contents:
     vrrp_script chk_ingress {
         script "/usr/bin/timeout 0.9 /usr/bin/curl -o /dev/null -Lfs http://localhost:1936/healthz/ready"
         interval 1
-        weight 20
         rise 3
         fall 2
     }