mysql secondary statefulset is not created

Name and Version

mysql-11.1.17

What architecture are you using?

Kubernetes cluster

Hello everyone,

I am attempting to deploy a MySQL cluster using the Bitnami Helm chart, but I am facing an issue where only the primary StatefulSet is created, even though I have configured the chart to include secondary nodes.

I ran this command helm template mysql-cluster bitnami/mysql --values newvalues.yml and checked the output and only saw primary set related configs

Here are the details of my setup: Helm Chart Information:

    Chart Name: Bitnami MySQL
    Helm Chart Version:mysql-11.1.17
    Kubernetes Version:1.30.0

Can someone please assist me with this?

Are you using any custom parameters or values?

auth:
  existingSecret: mysql-secret
  rootPasswordKey: mysql-root-password
  passwordKey: mysql-user-password
  replicationPasswordKey: mysql-replication-password

replication:
  enabled: true

primary:
  securityContext:
    runAsUser: 1001
    runAsGroup: 1001
    fsGroup: 1001
  persistence:
    enabled: true
    existingClaim: pvc-mysql-primary
  initContainers:
    - name: init-permissions
      image: bitnami/minideb:latest
      command: ["sh", "-c", "mkdir -p /bitnami/mysql/data; chown -R 1001:1001 /bitnami/mysql/data"]
      volumeMounts:
        - name: data
          mountPath: /bitnami/mysql/

secondary:
  enabled: true
  replicaCount: 2
  securityContext:
    runAsUser: 1001
    runAsGroup: 1001
    fsGroup: 1001
  persistence:
    enabled: true
    size: 10Gi
    storageClass: standard
  initContainers:
    - name: init-permissions
      image: bitnami/minideb:latest
      command: ["sh", "-c", "mkdir -p /bitnami/mysql/data; chown -R 1001:1001 /bitnami/mysql/data"]
      volumeMounts:
        - name: data
          mountPath: /bitnami/mysql/

What is the expected behavior?

Only create primary set

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and want to contribute a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

bitnami / charts