Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-03 06:58:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/tomcat,wildfly,consul] Fix upgrade repo

Browse Source 
Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
This commit is contained in:
Carlos Rodriguez Hernandez
2020-02-11 15:28:22 +00:00
parent 40ee57cf51
commit 3d3fdbea9e
6 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bitnami/consul/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: consul
version: 6.1.1
version: 6.1.2
appVersion: 1.6.3
description: Highly available and distributed service discovery and key-value store designed with support for the modern data center to make distributed systems and configuration easy.
home: https://www.consul.io/

4
bitnami/consul/README.md
View File

@@ -272,13 +272,13 @@ This release updates the Bitnami Consul container to `1.6.1-debian-9-r6`, which
Consul container was moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both the container image and the chart can be upgraded by running the command below:
```
$ helm upgrade my-release stable/consul
$ helm upgrade my-release bitnami/consul
```
If you use a previous container image (previous to **1.4.0-r16**) disable the `securityContext` by running the command below:
```
$ helm upgrade my-release stable/consul --set securityContext.enabled=fase,image.tag=XXX
$ helm upgrade my-release bitnami/consul --set securityContext.enabled=fase,image.tag=XXX
```
### To 2.0.0

2
bitnami/tomcat/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: tomcat
version: 6.2.1
version: 6.2.2
appVersion: 9.0.30
description: Chart for Apache Tomcat
keywords:

4
bitnami/tomcat/README.md
View File

@@ -154,13 +154,13 @@ This release updates the Bitnami Tomcat container to `9.0.26-debian-9-r0`, which
Tomcat container was moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both the container image and the chart can be upgraded by running the command below:
```
$ helm upgrade my-release stable/tomcat
$ helm upgrade my-release bitnami/tomcat
```
If you use a previous container image (previous to **8.5.35-r26**) disable the `securityContext` by running the command below:
```
$ helm upgrade my-release stable/tomcat --set securityContext.enabled=fase,image.tag=XXX
$ helm upgrade my-release bitnami/tomcat --set securityContext.enabled=fase,image.tag=XXX
```
### To 1.0.0

2
bitnami/wildfly/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: wildfly
version: 3.5.1
version: 3.5.2
appVersion: 18.0.1
description: Chart for Wildfly
keywords:

4
bitnami/wildfly/README.md
View File

@@ -142,13 +142,13 @@ You can enable this initContainer by setting `volumePermissions.enabled` to `tru
WildFly container was moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both the container image and the chart can be upgraded by running the command below:
```
$ helm upgrade my-release stable/wildfly
$ helm upgrade my-release bitnami/wildfly
```
If you use a previous container image (previous to **14.0.1-r75**) disable the `securityContext` by running the command below:
```
$ helm upgrade my-release stable/wildfly --set securityContext.enabled=fase,image.tag=XXX
$ helm upgrade my-release bitnami/wildfly --set securityContext.enabled=fase,image.tag=XXX
```
### To 1.0.0