Graham McIntire
bac286ee1b
Previously Valkey ran as a sidecar container in the main deployment, causing it to restart every time the web app deployed. This resulted in connection errors and cache loss during deployments. Changes: - Created valkey-statefulset.yaml with StatefulSet resource (1 replica) - Created valkey-service.yaml with headless service - Removed Valkey sidecar container from deployment.yaml - Updated REDIS_HOST from 127.0.0.1 to valkey-0.valkey.towerops.svc.cluster.local - Added new resources to kustomization.yaml Benefits: - Valkey persists across web app deployments - No connection errors during rolling updates - Cache data preserved - Independent scaling and resource management
65 lines
1.5 KiB
YAML
65 lines
1.5 KiB
YAML
---
|
|
apiVersion: apps/v1
|
|
kind: StatefulSet
|
|
metadata:
|
|
name: valkey
|
|
namespace: towerops
|
|
spec:
|
|
serviceName: valkey
|
|
replicas: 1
|
|
selector:
|
|
matchLabels:
|
|
app: valkey
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: valkey
|
|
spec:
|
|
securityContext:
|
|
runAsNonRoot: true
|
|
runAsUser: 999
|
|
fsGroup: 999
|
|
seccompProfile:
|
|
type: RuntimeDefault
|
|
containers:
|
|
- name: valkey
|
|
image: valkey/valkey:8.0-alpine
|
|
imagePullPolicy: IfNotPresent
|
|
securityContext:
|
|
allowPrivilegeEscalation: false
|
|
runAsNonRoot: true
|
|
runAsUser: 999
|
|
capabilities:
|
|
drop:
|
|
- ALL
|
|
seccompProfile:
|
|
type: RuntimeDefault
|
|
ports:
|
|
- containerPort: 6379
|
|
name: valkey
|
|
resources:
|
|
requests:
|
|
memory: "128Mi"
|
|
cpu: "50m"
|
|
limits:
|
|
memory: "512Mi"
|
|
cpu: "200m"
|
|
livenessProbe:
|
|
exec:
|
|
command:
|
|
- valkey-cli
|
|
- ping
|
|
initialDelaySeconds: 10
|
|
periodSeconds: 10
|
|
timeoutSeconds: 2
|
|
failureThreshold: 3
|
|
readinessProbe:
|
|
exec:
|
|
command:
|
|
- valkey-cli
|
|
- ping
|
|
initialDelaySeconds: 5
|
|
periodSeconds: 5
|
|
timeoutSeconds: 2
|
|
successThreshold: 1
|
|
failureThreshold: 2
|