From 7e9940c6193406c3005740be363758fd5fe7a96c Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Sun, 18 Jan 2026 11:23:51 -0600 Subject: [PATCH] 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 | 2 +- k8s/valkey-service.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/k8s/deployment.yaml b/k8s/deployment.yaml index 2c054cb8..5406eb10 100644 --- a/k8s/deployment.yaml +++ b/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: diff --git a/k8s/valkey-service.yaml b/k8s/valkey-service.yaml index e12f7252..b4e872d0 100644 --- a/k8s/valkey-service.yaml +++ b/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: