fix(sovereign-workplace-jitsi): Fix patchJVB breaking loop and let status field be customized

charts/sovereign-workplace-jitsi/templates/configmap.yaml

@@ -30,7 +30,7 @@ data:
     maxRetries=30
     until [ $counter -gt ${maxRetries} ]; do
     echo "Wait for LoadBalancer IP (${counter}/${maxRetries})"
-    ip=$(kubectl get svc jitsi-jvb -o jsonpath='{.status.loadBalancer.ingress[0].ip}');
+    ip=$(kubectl get svc jitsi-jvb -o jsonpath='{.status.loadBalancer.ingress[0].{{ .Values.patchJVB.configuration.loadbalancerStatusField }}' || true);
     if [ ${ip} ]; then
       break;
     else
@@ -38,6 +38,11 @@ data:
       sleep 5;
     fi
     done
+    if [ $counter -le 0 ]; then
+      echo "Reached retries limit, exiting..."
+      exit 1
+    fi;
+
     echo "Patching JVB to advertise IP: ${ip}"
     kubectl patch cm jitsi-jvb --type json --patch \
       "[{ \"op\": \"add\", \"path\": \"/data/JVB_ADVERTISE_IPS\", \"value\": \"${ip}\" },

charts/sovereign-workplace-jitsi/values.yaml

@@ -92,6 +92,11 @@ patchJVB:
     # your ingress gateway.
     staticLoadbalancerIP: ""
 
+    # -- Relevant for LoadBalancer deployment only.
+    # The IP/DNS of your load-balancer will be fetched from the status entry of service - here you can define which
+    # field should be taken.
+    loadbalancerStatusField: "ip"
+
   # Security Context.
   # Ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
   containerSecurityContext: