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:
Erick Calder
  • 31

1 Answers1

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: []
Erick Calder
  • 31