2

we are running Redis as a container in a Kubernetes cluster (v1.21.14-gke.3000) where it is installed via Helm. Helm uses the Bitnami image, which disables the FLUSHALL command. As with this article, we want to re-enable Redis command but editing the configuration file is not feasible. is there an alternative?

below is my helmfile.yaml:

repositories:
- name: bitnami
  url: https://charts.bitnami.com/bitnami

environments:
  dev:
    values:
      - existingSecret: 'redis-secret'
      - redisVersion: 17.3.8
  prod:
    values:
      - existingSecret: 'redis-secret'
      - redisVersion: 17.3.8

releases:
- name: redis
  namespace: gitlab-managed-apps
  chart: bitnami/redis
  version: "{{ .Values.redisVersion }}"
  installed: true
  recreatePods: true
  values:
    - values.yaml.gotmpl

and the corresponding values.yaml.gotmpl:

auth:
  enabled: true
  existingSecret: {{ .Values.existingSecret }}

global:
  storageClass: 'premium-rwo'
  redis:
    password: "***"
replica:
  replicaCount: 1
master:
2
  • Hi Erick Calder welcome to S.F. You'll want to edit your question and include the details of your install, such as the chart version and any --values or --set you used, since as written no one can guess what you've done or look up the docker image to have any context for your question. Good luck
    – mdaniel
    Commented Nov 6, 2022 at 1:24
  • @mdaniel thanks for the constructive criticism. I've added the relevant files, which should be enough (I think) as context Commented Nov 6, 2022 at 2:11

1 Answer 1

1

after pulling my hair for a time I figured out the answer. I can use the disableCommands value, which has to be handed to both the master and the replica like this: and the corresponding values.yaml.gotmpl:

master:
  disableCommands: []
replica:
  disableCommands: []

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .