Stop supporting values_production.yaml

[carrodher]

Some of the Bitnami Helm Charts (40 of 80) contain a values-production.yaml file apart from the values.yaml. The content of both values files is practically the same but the production ones have different default values in some parameters, being the most common metrics enabled, number of replicas, forced to specify a password, forced a URL, TLS enabled, and more.

There are no clear guidelines as to what is considered "production", as this concept of "production" varies according to the use case or need of each user. This is the principal reason why the Bitnami team is planning to remove the values-production.yaml file in favor of providing flexibility and documentation so each user can customize the default values.yaml to their particular needs.

Apart from that, there are other reasons behind this decision such as the lack of proper tests covering custom values files like the values_production.yaml, difficulty to maintain in sync values.yaml and values-production.yaml, need to place the values file in the host or specify it via URL, among others.

values-production.yaml removal status

• airflow
• aspnet-core
• cassandra
• consul
• discourse
• elasticsearch
• etcd
• external-dns
• fluentd
• grafana
• harbor
• influxdb
• kafka
• kibana
• kong
• kube-prometheus
• kube-state-metrics
• logstash
• magento
• mariadb
• mariadb-galera
• memcached
• minio
• mongodb
• mongodb-sharded
• mxnet
• mysql
• nats
• nginx-ingress-controller
• postgresql
• postgresql-ha
• pytorch
• rabbitmq
• redis
• redis-cluster
• spark
• spring-cloud-dataflow
• thanos
• wordpress
• zookeeper

[carrodher]

All the Helm Charts have being released without the values-production.yaml