fix: resource tuning — LiveKit Recreate strategy, OpenSearch JVM heap, login-ui

LiveKit: switch to Recreate deployment strategy. hostPorts (TURN UDP relay
range) block RollingUpdate because the new pod cannot schedule while the
old one still holds the ports.

OpenSearch: set OPENSEARCH_JAVA_OPTS to -Xms192m -Xmx256m. The upstream
default (-Xms512m -Xmx1g) immediately OOMs the container given our 512Mi
memory limit.

login-ui: raise memory limit from 64Mi to 192Mi and add a 64Mi request;
the previous limit was too tight and caused OOMKilled restarts under load.

base/media/livekit-values.yaml

@@ -36,3 +36,8 @@ deployment:
     requests:
       memory: 64Mi
       cpu: 100m
+
+# Recreate strategy: hostPorts (TURN UDP relay range) block RollingUpdate —
+# the new pod cannot schedule while the old one still holds the host ports.
+deploymentStrategy:
+  type: Recreate

overlays/local/values-resources.yaml

@@ -74,9 +74,16 @@ spec:
     spec:
       containers:
         - name: opensearch
+          env:
+            # Reduce JVM heap so it fits within the 512Mi container limit.
+            # Base sets -Xms512m -Xmx1g which immediately OOMs the container.
+            - name: OPENSEARCH_JAVA_OPTS
+              value: "-Xms192m -Xmx256m"
           resources:
             limits:
               memory: 512Mi
+            requests:
+              memory: 256Mi
 
 ---
 apiVersion: apps/v1
@@ -121,6 +128,8 @@ spec:
         - name: login-ui
           resources:
             limits:
+              memory: 192Mi
+            requests:
               memory: 64Mi
 
 ---