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

[bitnami/several] Unify upgrading section

Browse Source
This commit is contained in:
Carlos Rodriguez Hernandez
2021-08-02 12:35:34 +00:00
parent 6b55d2232c
commit baf228384a
10 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/jasperreports/README.md
View File

@@ -393,11 +393,11 @@ mariadb 12:13:25.01 INFO ==> Running mysql_upgrade
...
```
### to 8.0.0
### To 8.0.0
JasperReports 7.5.0 includes some new configuration options that are required to be added if you upgrade from previous versions. Please check the [official community guide](https://community.jaspersoft.com/documentation/tibco-jasperreports-server-upgrade-guide/v750/upgrading-72-75) to upgrade your previous JasperReports installation.
### 7.0.0
### To 7.0.0
Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
@@ -405,7 +405,7 @@ In https://github.com/helm/charts/pull/17298 the `apiVersion` of the deployment
This major version signifies this change.
### 3.0.0
### To 3.0.0
Backwards compatibility is not guaranteed unless you modify the labels used on the chart's deployments.
Use the workaround below to upgrade from versions previous to 3.0.0. The following example assumes that the release name is jasperreports: