MariaDB metrics container duplicate "env:" key

[cgorman]

Name and Version

bitnami/mariadb 24.0.2

What steps will reproduce the bug?

With the provided values.yaml (i.e. metrics enabled), perform a standard deployment of MariaDB.

Are you using any custom parameters or values?

metrics:
  enabled: true
  extraArgs:
    primary:
      - --collect.auto_increment.columns
      - --collect.binlog_size
      - --collect.engine_innodb_status
      - --collect.engine_tokudb_status
      - --collect.global_status
      - --collect.global_variables
      - --collect.info_schema.clientstats
      - --collect.info_schema.innodb_metrics
      - --collect.info_schema.innodb_tablespaces
      - --collect.info_schema.innodb_cmp
      - --collect.info_schema.innodb_cmpmem
      - --collect.info_schema.processlist
      - --collect.info_schema.processlist.min_time
      - --collect.info_schema.query_response_time
      - --collect.info_schema.tables
      - --collect.info_schema.tables.databases
      - --collect.info_schema.tablestats
      - --collect.info_schema.userstats
      - --collect.perf_schema.eventsstatements
      - --collect.perf_schema.eventsstatements.digest_text_limit
      - --collect.perf_schema.eventsstatements.limit
      - --collect.perf_schema.eventsstatements.timelimit
      - --collect.perf_schema.eventswaits
      - --collect.perf_schema.file_events
      - --collect.perf_schema.file_instances
      - --collect.perf_schema.indexiowaits
      - --collect.perf_schema.tableiowaits
      - --collect.perf_schema.tablelocks
      - --collect.perf_schema.replication_group_member_stats
      - --collect.slave_status
      - --collect.slave_hosts
      - --collect.heartbeat
      - --collect.heartbeat.database
      - --collect.heartbeat.table

  containerPorts:
    http: 9104
  containerSecurityContext:
    enabled: true
    privileged: false
    runAsNonRoot: true
    seLinuxOptions: {}
    runAsUser: 1001
    runAsGroup: 1001
    readOnlyRootFilesystem: true
    allowPrivilegeEscalation: false
    capabilities:
      drop: ["ALL"]
    seccompProfile:
      type: "RuntimeDefault"

  resourcesPreset: "micro"

  serviceMonitor:
    enabled: true
    namespace: "cattle-monitoring-system"

What is the expected behavior?

Deployment succeeds.

What do you see instead?

Error: INSTALLATION FAILED: error while running post render on files: error while running command /usr/local/bin/skaffold. error output:
reading Kubernetes YAML: yaml: unmarshal errors:
  line 274: mapping key "env" already defined at line 232

Additional information

I believe this error is because of the extra env mapping in the metrics definition, primary/statefulset.yaml lines 407-413. I assume this is also the case for the secondary, but I haven't checked.

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing 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.

[cgorman]

It looks like the chart I'm using doesn't match the contents of the repo, is 24.0.2 being tracked somewhere else, or should I not be using https://charts.bitnami.com/bitnami?

[carrodher]

With the changes announced at #35164, the Helm chart source code present in this repository continues to be available under the Apache 2 license. However, we have stopped packaging, testing, and publishing the charts as a "final package"; this is something that needs to be done by the user (forking the repo and running helm package. Pre-built Helm charts are only available under the Bitnami Secure Images subscription.

Please take a look at the pinned issue linked above for full details.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.