OliverKleinBST commented on issue #34414: URL: https://github.com/apache/superset/issues/34414#issuecomment-3361829507
> We got rid of any Redis interactions once and for all using Valkey: > > * deployment.yaml > > apiVersion: apps/v1 > kind: Deployment > metadata: > name: valkey > namespace: the-namespace > spec: > selector: > matchLabels: > app: valkey > template: > metadata: > labels: > app: valkey > spec: > containers: > - name: valkey > image: valkey/valkey:9.0-alpine3.22 > ports: > - name: server > containerPort: 6379 > livenessProbe: > periodSeconds: 300 > tcpSocket: > port: server > readinessProbe: > exec: > command: ["valkey-cli", "ping", "|", "grep", "PONG"] > initialDelaySeconds: 30 > periodSeconds: 300 > * service.yaml > > apiVersion: v1 > kind: Service > metadata: > name: valkey > namespace: the-namespace > labels: > app: valkey > spec: > type: ClusterIP > ports: > - port: 6379 > targetPort: 6379 > protocol: TCP > name: valkey > selector: > app: valkey > * values.yaml > > ... > redis: > enabled: false > supersetNode: > connections: > redis_host: valkey.the-namespace.svc.cluster.local > ... very nice. I also thought moving to valkey when that Bitnami issue started - to find myself into the only useful helmchart for valkey came from Bitnami.... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
