towerops/k8s/valkey-service.yaml
Graham McIntire 7e9940c619
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.
2026-01-18 11:23:51 -06:00

14 lines
200 B
YAML

---
apiVersion: v1
kind: Service
metadata:
name: valkey
namespace: towerops
spec:
type: ClusterIP
selector:
app: valkey
ports:
- port: 6379
targetPort: 6379
name: valkey