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

[bitnami/jasperreports] Release 12.0.5 updating components versions

Browse Source 
Signed-off-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Bitnami Containers
2022-02-12 13:41:07 +00:00
parent 3323f59c38
commit e1abad4fad
4 changed files with 53 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/jasperreports/Chart.lock
View File

@@ -1,9 +1,9 @@
dependencies:
- name: mariadb
repository: https://charts.bitnami.com/bitnami
version: 10.3.1
version: 10.3.3
- name: common
repository: https://charts.bitnami.com/bitnami
version: 1.10.3
digest: sha256:8d2dc3f109e1e2bd70762561ef4ec64c2f2b25c702ced2bb4666c561c454a857
generated: "2022-01-13T12:43:57.307304889Z"
version: 1.11.1
digest: sha256:2cc036a02156d5c4ee45373d949d5e5232d4987829768584443b7131e8502461
generated: "2022-02-12T00:13:52.58066391Z"

4
bitnami/jasperreports/Chart.yaml
View File

@@ -12,7 +12,7 @@ dependencies:
tags:
- bitnami-common
version: 1.x.x
description: The JasperReports server can be used as a stand-alone or embedded reporting and BI server that offers web-based reporting, analytic tools and visualization, and a dashboard feature for compiling multiple custom views
description: JasperReports Server is a stand-alone and embeddable reporting server. It is a central information hub, with reporting and analytics that can be embedded into web and mobile applications.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/jasperreports
icon: https://bitnami.com/assets/stacks/jasperserver/img/jasperserver-stack-220x234.png
@@ -30,4 +30,4 @@ name: jasperreports
sources:
- https://github.com/bitnami/bitnami-docker-jasperreports
- http://community.jaspersoft.com/project/jasperreports-server
version: 12.0.4
version: 12.0.5

56
bitnami/jasperreports/README.md
View File

@@ -1,9 +1,13 @@
<!--- app-name: JasperReports -->
<!--- app-name: Jasper&reg;eports -->
# JasperReports
# Jasper&reg;eports packaged by Bitnami
[JasperReports](http://community.jaspersoft.com/project/jasperreports-server) The JasperReports server can be used as a stand-alone or embedded reporting and BI server that offers web-based reporting, analytic tools and visualization, and a dashboard feature for compiling multiple custom views
Jasper&reg;eports Server is a stand-alone and embeddable reporting server. It is a central information hub, with reporting and analytics that can be embedded into web and mobile applications.
[Overview of Jasper&reg;eports](http://community.jaspersoft.com/project/jasperreports-server)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -13,9 +17,9 @@ $ helm install my-release bitnami/jasperreports
## Introduction
This chart bootstraps a [JasperReports](https://github.com/bitnami/bitnami-docker-jasperreports) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
This chart bootstraps a [Jasper&reg;eports](https://github.com/bitnami/bitnami-docker-jasperreports) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which bootstraps a MariaDB deployment required by the JasperReports application.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which bootstraps a MariaDB deployment required by the Jasper&reg;eports application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the [BKPR](https://kubeprod.io/).
@@ -34,7 +38,7 @@ To install the chart with the release name `my-release`:
$ helm install my-release bitnami/jasperreports
```
The command deploys JasperReports on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
The command deploys Jasper&reg;eports on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
> **Tip**: List all releases using `helm list`
@@ -72,18 +76,18 @@ The command removes all the Kubernetes components associated with the chart and
| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |
### JasperReports parameters
### Jasper&reg;eports parameters
| Name | Description | Value |
| ----------------------- | ---------------------------------------------------------------------- | ----------------------- |
| `image.registry` | JasperReports image registry | `docker.io` |
| `image.repository` | JasperReports image repository | `bitnami/jasperreports` |
| `image.tag` | JasperReports image tag (immutable tags are recommended) | `7.8.1-debian-10-r57` |
| `image.pullPolicy` | JasperReports image pull policy | `IfNotPresent` |
| `image.registry` | Jasper&reg;eports image registry | `docker.io` |
| `image.repository` | Jasper&reg;eports image repository | `bitnami/jasperreports` |
| `image.tag` | Jasper&reg;eports image tag (immutable tags are recommended) | `7.8.1-debian-10-r57` |
| `image.pullPolicy` | Jasper&reg;eports image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `jasperreportsUsername` | JasperReports user | `jasperadmin` |
| `jasperreportsPassword` | JasperReports password | `""` |
| `jasperreportsEmail` | JasperReports user email | `user@example.com` |
| `jasperreportsUsername` | Jasper&reg;eports user | `jasperadmin` |
| `jasperreportsPassword` | Jasper&reg;eports password | `""` |
| `jasperreportsEmail` | Jasper&reg;eports user email | `user@example.com` |
| `allowEmptyPassword` | Set to `yes` to allow the container to be started with blank passwords | `no` |
| `smtpHost` | SMTP host | `""` |
| `smtpPort` | SMTP port | `""` |
@@ -146,7 +150,7 @@ The command removes all the Kubernetes components associated with the chart and
| `affinity` | Affinity for pod assignment | `{}` |
| `nodeSelector` | Node labels for pod assignment | `{}` |
| `tolerations` | Tolerations for pod assignment | `[]` |
| `priorityClassName` | JasperReports pods' priorityClassName | `""` |
| `priorityClassName` | Jasper&reg;eports pods' priorityClassName | `""` |
| `schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `lifecycleHooks` | LifecycleHooks to set additional configuration at startup. | `{}` |
@@ -243,7 +247,7 @@ $ helm install my-release \
bitnami/jasperreports
```
The above command sets the JasperReports administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
The above command sets the Jasper&reg;eports administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
> NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.
@@ -265,7 +269,7 @@ Bitnami will release a new chart updating its containers if a new version of the
## Persistence
The [Bitnami JasperReports](https://github.com/bitnami/bitnami-docker-jasperreports) image stores the JasperReports data and configurations at the `/bitnami/jasperreports` path of the container.
The [Bitnami Jasper&reg;eports](https://github.com/bitnami/bitnami-docker-jasperreports) image stores the Jasper&reg;eports data and configurations at the `/bitnami/jasperreports` path of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
See the [Parameters](#parameters) section to configure the PVC or to disable persistence.
@@ -284,7 +288,7 @@ Alternatively, you can use a ConfigMap or a Secret with the environment variable
### Sidecars and Init Containers
If you have a need for additional containers to run within the same pod as the JasperReports app (e.g. an additional metrics or logging exporter), you can do so via the `sidecars` config parameter. Simply define your container according to the Kubernetes container spec.
If you have a need for additional containers to run within the same pod as the Jasper&reg;eports app (e.g. an additional metrics or logging exporter), you can do so via the `sidecars` config parameter. Simply define your container according to the Kubernetes container spec.
```yaml
sidecars:
@@ -334,14 +338,14 @@ Additionally updates the MariaDB subchart to it newest major, 10.0.0, which cont
### To 11.0.0
The [Bitnami JasperReports](https://github.com/bitnami/bitnami-docker-jasperreports) image was migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Tomcat daemon was started as the `tomcat` user. From now on, both the container and the Tomcat daemon run as user `1001`. You can revert this behavior by setting the parameters `containerSecurityContext.runAsUser` to `root`.
The [Bitnami Jasper&reg;eports](https://github.com/bitnami/bitnami-docker-jasperreports) image was migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Tomcat daemon was started as the `tomcat` user. From now on, both the container and the Tomcat daemon run as user `1001`. You can revert this behavior by setting the parameters `containerSecurityContext.runAsUser` to `root`.
Consequences:
- The HTTP/HTTPS ports exposed by the container are now `8080/8443` instead of `80/443`.
- Backwards compatibility is not guaranteed.
To upgrade to `11.0.0`, backup JasperReports data and the previous MariaDB databases, install a new JasperReports chart and import the backups and data, ensuring the `1001` user has the appropriate permissions on the migrated volume.
To upgrade to `11.0.0`, backup Jasper&reg;eports data and the previous MariaDB databases, install a new Jasper&reg;eports chart and import the backups and data, ensuring the `1001` user has the appropriate permissions on the migrated volume.
In addition to this, the image was refactored and now the source code is published in GitHub in the [`rootfs`](https://github.com/bitnami/bitnami-docker-jasperreports/tree/master/7/debian-10/rootfs) folder of the container image.
@@ -354,7 +358,7 @@ We also fixed a regression with readiness and liveness probes. Now the kind of p
Consequences:
- Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing JasperReports deployment before upgrading (the following example assumes that the release name is `jasperreports`):
- Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Jasper&reg;eports deployment before upgrading (the following example assumes that the release name is `jasperreports`):
```console
$ export JASPER_PASSWORD=$(kubectl get secret --namespace default jasperreports -o jsonpath="{.data.jasperreports-password}" | base64 --decode)
@@ -400,11 +404,11 @@ Please read the update notes carefully.
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the MariaDB and JasperReports data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is `jasperreports` and that a `rootUser.password` was defined for MariaDB in `values.yaml` when the chart was first installed):
To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the MariaDB and Jasper&reg;eports data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is `jasperreports` and that a `rootUser.password` was defined for MariaDB in `values.yaml` when the chart was first installed):
> NOTE: Please, create a backup of your database before running any of those actions. The steps below would be only valid if your application (e.g. any plugins or custom code) is compatible with MariaDB 10.5.x
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and JasperReports data on your current release:
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and Jasper&reg;eports data on your current release:
```console
export JASPERREPORTS_PASSWORD=$(kubectl get secret --namespace default jasperreports -o jsonpath="{.data.jasperreports-password}" | base64 --decode)
@@ -413,7 +417,7 @@ export MARIADB_PASSWORD=$(kubectl get secret --namespace default jasperreports-m
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=jasperreports -o jsonpath="{.items[0].metadata.name}")
```
Delete the JasperReports deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter:
Delete the Jasper&reg;eports deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter:
```console
$ kubectl delete deployments.apps jasperreports
@@ -445,7 +449,7 @@ mariadb 12:13:25.01 INFO ==> Running mysql_upgrade
### 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.
Jasper&reg;eports 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 Jasper&reg;eports installation.
### To 7.0.0
@@ -487,4 +491,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.

34
bitnami/jasperreports/values.yaml
View File

@@ -42,21 +42,21 @@ clusterDomain: cluster.local
##
extraDeploy: []
## @section JasperReports parameters
## @section Jasper&reg;eports parameters
##
## Bitnami JasperReports image version
## Bitnami Jasper&reg;eports image version
## ref: https://hub.docker.com/r/bitnami/dokuwiki/tags/
## @param image.registry JasperReports image registry
## @param image.repository JasperReports image repository
## @param image.tag JasperReports image tag (immutable tags are recommended)
## @param image.pullPolicy JasperReports image pull policy
## @param image.registry Jasper&reg;eports image registry
## @param image.repository Jasper&reg;eports image repository
## @param image.tag Jasper&reg;eports image tag (immutable tags are recommended)
## @param image.pullPolicy Jasper&reg;eports image pull policy
## @param image.pullSecrets Specify docker-registry secret names as an array
##
image:
registry: docker.io
repository: bitnami/jasperreports
tag: 7.8.1-debian-10-r57
tag: 7.8.1-debian-10-r69
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -70,16 +70,16 @@ image:
## - myRegistryKeySecretName
##
pullSecrets: []
## @param jasperreportsUsername JasperReports user
## @param jasperreportsUsername Jasper&reg;eports user
## ref: https://github.com/bitnami/bitnami-docker-jasperreports#configuration
##
jasperreportsUsername: jasperadmin
## @param jasperreportsPassword JasperReports password
## @param jasperreportsPassword Jasper&reg;eports password
## Defaults to a random 10-character alphanumeric string if not set
## ref: https://github.com/bitnami/bitnami-docker-jasperreports#configuration
##
jasperreportsPassword: ""
## @param jasperreportsEmail JasperReports user email
## @param jasperreportsEmail Jasper&reg;eports user email
## ref: https://github.com/bitnami/bitnami-docker-jasperreports#configuration
##
jasperreportsEmail: user@example.com
@@ -140,7 +140,7 @@ hostAliases: []
##
containerPorts:
http: 8080
## JasperReports pods' Security Context
## Jasper&reg;eports pods' Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
## @param podSecurityContext.enabled Enable pod's Security Context
## @param podSecurityContext.fsGroup Set pod's Security Context fsGroup
@@ -148,7 +148,7 @@ containerPorts:
podSecurityContext:
enabled: true
fsGroup: 1001
## JasperReports containers' SecurityContext
## Jasper&reg;eports containers' SecurityContext
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param containerSecurityContext.enabled Enable container's Security Context
## @param containerSecurityContext.runAsUser Set container's Security Context runAsUser
@@ -158,7 +158,7 @@ containerSecurityContext:
enabled: true
runAsUser: 1001
runAsNonRoot: true
## JasperReports resource requests and limits
## Jasper&reg;eports resource requests and limits
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## We usually recommend not to specify default resources and to leave this as a conscious
## choice for the user. This also increases chances charts run on environments with little
@@ -177,7 +177,7 @@ resources:
requests:
memory: 512Mi
cpu: 300m
## JasperReports containers' liveness, readiness and startup probes.
## Jasper&reg;eports containers' liveness, readiness and startup probes.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param startupProbe.enabled Enable startupProbe
## @param startupProbe.path Request path for startupProbe
@@ -211,7 +211,7 @@ livenessProbe:
timeoutSeconds: 5
failureThreshold: 6
successThreshold: 1
## JasperReports containers' readiness probe
## Jasper&reg;eports containers' readiness probe
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param readinessProbe.enabled Enable readinessProbe
## @param readinessProbe.path Request path for readinessProbe
@@ -286,7 +286,7 @@ nodeSelector: {}
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
## @param priorityClassName JasperReports pods' priorityClassName
## @param priorityClassName Jasper&reg;eports pods' priorityClassName
##
priorityClassName: ""
## @param schedulerName Name of the k8s scheduler (other than default)
@@ -417,7 +417,7 @@ service:
sessionAffinityConfig: {}
## Configure the ingress resource that allows you to access the
## JasperReports installation. Set up the URL
## Jasper&reg;eports installation. Set up the URL
## ref: https://kubernetes.io/docs/user-guide/ingress/
##
ingress: