diff --git a/bitnami/elasticsearch/README.md b/bitnami/elasticsearch/README.md index 65d4d3e0c..5acc08515 100644 --- a/bitnami/elasticsearch/README.md +++ b/bitnami/elasticsearch/README.md @@ -453,6 +453,10 @@ This chart includes a `values-production.yaml` file where you can find some para + global.kibanaEnabled: true ``` +### Change ElasticSearch version + +To modify the ElasticSearch version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/elasticsearch/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Default kernel settings Currently, Elasticsearch requires some changes in the kernel of the host machine to work as expected. If those values are not set in the underlying operating system, the ES containers fail to boot with ERROR messages. More information about these requirements can be found in the links below: diff --git a/bitnami/kibana/README.md b/bitnami/kibana/README.md index f0ff89625..ecd945af7 100644 --- a/bitnami/kibana/README.md +++ b/bitnami/kibana/README.md @@ -175,6 +175,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change Kibana version + +To modify the Kibana version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/kibana/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Using custom configuration The Bitnami Kibana chart supports using custom configuration settings. For example, to mount a custom `kibana.yml` you can create a ConfigMap like the following: diff --git a/bitnami/mariadb-galera/README.md b/bitnami/mariadb-galera/README.md index f4a930cba..6cef5b96d 100644 --- a/bitnami/mariadb-galera/README.md +++ b/bitnami/mariadb-galera/README.md @@ -234,6 +234,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change MariaDB version + +To modify the MariaDB version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/mariadb-galera/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### LDAP LDAP support can be enabled in the chart by specifying the `ldap.` parameters while creating a release. The following parameters should be configured to properly enable the LDAP support in the chart. diff --git a/bitnami/mariadb/README.md b/bitnami/mariadb/README.md index f3900d6bd..80640c287 100644 --- a/bitnami/mariadb/README.md +++ b/bitnami/mariadb/README.md @@ -264,6 +264,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change MariaDB version + +To modify the MariaDB version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/mariadb/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Initialize a fresh instance The [Bitnami MariaDB](https://github.com/bitnami/bitnami-docker-mariadb) image allows you to use your custom scripts to initialize a fresh instance. In order to execute the scripts, they must be located inside the chart folder `files/docker-entrypoint-initdb.d` so they can be consumed as a ConfigMap. diff --git a/bitnami/mongodb-sharded/README.md b/bitnami/mongodb-sharded/README.md index 45523d70c..02ad21c37 100644 --- a/bitnami/mongodb-sharded/README.md +++ b/bitnami/mongodb-sharded/README.md @@ -337,6 +337,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change MongoDB version + +To modify the MongoDB version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/mongodb-sharded/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Sharding This chart deploys a sharded cluster by default. Some characteristics of this chart are: diff --git a/bitnami/mongodb/README.md b/bitnami/mongodb/README.md index 91cbc70c1..ba9827778 100644 --- a/bitnami/mongodb/README.md +++ b/bitnami/mongodb/README.md @@ -248,6 +248,10 @@ This chart includes a `values-production.yaml` file where you can find some para To horizontally scale this chart, you can use the `--replicas` flag to modify the number of secondary nodes in your MongoDB replica set. +### Change MongoDB version + +To modify the MongoDB version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/mongodb/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Replication You can start the MongoDB chart in replica set mode with the following parameter: `replicaSet.enabled=true` diff --git a/bitnami/mysql/README.md b/bitnami/mysql/README.md index 20d68594f..ecbffdb04 100644 --- a/bitnami/mysql/README.md +++ b/bitnami/mysql/README.md @@ -226,6 +226,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change MySQL version + +To modify the MySQL version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/mysql/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Initialize a fresh instance The [Bitnami MySQL](https://github.com/bitnami/bitnami-docker-mysql) image allows you to use your custom scripts to initialize a fresh instance. In order to execute the scripts, they must be located inside the chart folder `files/docker-entrypoint-initdb.d` so they can be consumed as a ConfigMap. diff --git a/bitnami/nginx/README.md b/bitnami/nginx/README.md index 6c73c959f..b8cf9fc4f 100644 --- a/bitnami/nginx/README.md +++ b/bitnami/nginx/README.md @@ -177,6 +177,10 @@ It is strongly recommended to use immutable tags in a production environment. Th Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. +### Change NGINX version + +To modify the NGINX version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/nginx/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Deploying your custom web application The NGINX chart allows you to deploy a custom web application using one of the following methods: diff --git a/bitnami/node/README.md b/bitnami/node/README.md index f2fc37f68..9ea8095f0 100644 --- a/bitnami/node/README.md +++ b/bitnami/node/README.md @@ -140,6 +140,10 @@ It is strongly recommended to use immutable tags in a production environment. Th Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. +### Change Node version + +To modify the Node version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/node/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Set up an Ingress controller First install the nginx-ingress controller and then deploy the node helm chart with the following parameters: diff --git a/bitnami/odoo/README.md b/bitnami/odoo/README.md index 8c94c51b0..ebb27e6c6 100644 --- a/bitnami/odoo/README.md +++ b/bitnami/odoo/README.md @@ -144,6 +144,10 @@ It is strongly recommended to use immutable tags in a production environment. Th Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. +### Change Odoo version + +To modify the Odoo version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/odoo/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Using an external database Sometimes you may want to have Odoo connect to an external database rather than installing one inside your cluster, e.g. to use a managed database service, or use a single database server for all your applications. To do this, the chart allows you to specify credentials for an external database under the [`externalDatabase` parameter](#parameters). You should also disable the PostgreSQL installation with the `postgresql.enabled` option. For example using the following parameters: diff --git a/bitnami/postgresql-ha/README.md b/bitnami/postgresql-ha/README.md index 01822db4f..1cfda1933 100644 --- a/bitnami/postgresql-ha/README.md +++ b/bitnami/postgresql-ha/README.md @@ -265,7 +265,7 @@ To horizontally scale this chart, you can use the `--replicaCount` flag to modif ### Change PostgreSQL version -To modify the PostgreSQL version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/postgresql/tags/) using the `image.tag` parameter. For example, `image.tag=12.0.0` +To modify the PostgreSQL version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/postgresql-repmgr/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. ### Configure the way how to expose PostgreSQL diff --git a/bitnami/postgresql/README.md b/bitnami/postgresql/README.md index 70a544a09..1b99be927 100644 --- a/bitnami/postgresql/README.md +++ b/bitnami/postgresql/README.md @@ -292,7 +292,7 @@ At the top level, there is a service object which defines the services for both ### Change PostgreSQL version -To modify the PostgreSQL version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/postgresql/tags/) using the `image.tag` parameter. For example, `image.tag=12.0.0` +To modify the PostgreSQL version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/postgresql/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. ### postgresql.conf / pg_hba.conf files as configMap diff --git a/bitnami/redis-cluster/README.md b/bitnami/redis-cluster/README.md index a7908ac46..a6376372d 100644 --- a/bitnami/redis-cluster/README.md +++ b/bitnami/redis-cluster/README.md @@ -278,6 +278,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change Redis version + +To modify the Redis version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis-cluster/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Cluster topology The Helm Chart will deploy by default 3 redis masters and 3 replicas. By default the Redis Cluster is not accessible from outside the Kubernetes cluster, to access the Redis Cluster from outside you have to set `cluster.externalAccess.enabled=true` at deployment time. It will create in the first installation only 6 LoadBalancer services, one for each Redis node, once you have the external IPs of each service you will need to perform an upgrade passing those IPs to the `cluster.externalAccess.service.loadbalancerIP` array. diff --git a/bitnami/redis/README.md b/bitnami/redis/README.md index 45cef57aa..fa2ee908d 100644 --- a/bitnami/redis/README.md +++ b/bitnami/redis/README.md @@ -310,6 +310,10 @@ This chart includes a `values-production.yaml` file where you can find some para + metrics.enabled: true ``` +### Change Redis version + +To modify the Redis version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ### Cluster topologies #### Default: Master-Slave diff --git a/bitnami/tomcat/README.md b/bitnami/tomcat/README.md index 3b0d38455..506d25cf2 100644 --- a/bitnami/tomcat/README.md +++ b/bitnami/tomcat/README.md @@ -125,6 +125,10 @@ It is strongly recommended to use immutable tags in a production environment. Th Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist. +### Change Tomcat version + +To modify the Tomcat version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/tomcat/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters. + ## Persistence The [Bitnami Tomcat](https://github.com/bitnami/bitnami-docker-tomcat) image stores the Tomcat data and configurations at the `/bitnami/tomcat` path of the container.