fix(k8s): use ClusterIP service and FQDN for Valkey connection

Changed Valkey service from headless to ClusterIP and updated
REDIS_HOST to use full FQDN for more reliable DNS resolution.

Changes:
- valkey-service.yaml: Changed from headless (clusterIP: None) to ClusterIP
- deployment.yaml: Changed REDIS_HOST from "valkey" to "valkey.towerops.svc.cluster.local"

This ensures stable ClusterIP and explicit DNS resolution for Redis connections.

k8s/deployment.yaml

@@ -86,7 +86,7 @@ spec:
                   key: SECRET_KEY_BASE
             # Redis connection to standalone Valkey StatefulSet
             - name: REDIS_HOST
-              value: "valkey-0.valkey.towerops.svc.cluster.local"
+              value: "valkey.towerops.svc.cluster.local"
             - name: REDIS_PORT
               value: "6379"
           envFrom:

k8s/valkey-service.yaml

@@ -5,7 +5,7 @@ metadata:
   name: valkey
   namespace: towerops
 spec:
-  clusterIP: None  # Headless service for StatefulSet
+  type: ClusterIP
   selector:
     app: valkey
   ports: