[bitnami/testlink] Major version. Adapt Chart to apiVersion: v2 (#4316)

* [bitnami/testlink] Major version. Adapt Chart to apiVersion: v2

* [bitnami/testlink] Update components versions

Signed-off-by: Bitnami Containers <containers@bitnami.com>

Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Carlos Rodríguez Hernández
2020-11-11 22:48:18 +01:00
committed by GitHub
parent b1d47540da
commit b73dbdc23c
6 changed files with 56 additions and 33 deletions

View File

@@ -0,0 +1,9 @@
dependencies:
- name: mariadb
repository: https://charts.bitnami.com/bitnami
version: 9.0.0
- name: common
repository: https://charts.bitnami.com/bitnami
version: 1.0.0
digest: sha256:15fe4b2dd0a14e80e43e1a9f6dd23e0cbbe47549f709fc4f69f880e953f26184
generated: "2020-11-11T18:37:17.051375057Z"

View File

@@ -1,21 +1,31 @@
apiVersion: v1
name: testlink
version: 8.0.2
annotations:
category: DeveloperTools
apiVersion: v2
appVersion: 1.9.20
dependencies:
- condition: mariadb.enabled
name: mariadb
repository: https://charts.bitnami.com/bitnami
version: 9.x.x
- name: common
repository: https://charts.bitnami.com/bitnami
tags:
- bitnami-common
version: 1.x.x
description: Web-based test management system that facilitates software quality assurance.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/testlink
icon: https://bitnami.com/assets/stacks/testlink/img/testlink-stack-220x234.png
keywords:
- testlink
- testing
- http
- php
home: https://github.com/bitnami/charts/tree/master/bitnami/testlink
maintainers:
- email: containers@bitnami.com
name: Bitnami
name: testlink
sources:
- https://github.com/bitnami/bitnami-docker-testlink
- http://www.testlink.org/
maintainers:
- name: Bitnami
email: containers@bitnami.com
engine: gotpl
annotations:
category: DeveloperTools
version: 9.0.0

View File

@@ -20,7 +20,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
## Prerequisites
- Kubernetes 1.12+
- Helm 2.12+ or Helm 3.0-beta3+
- Helm 3.0-beta3+
- PV provisioner support in the underlying infrastructure
- ReadWriteMany volumes for deployment scaling
@@ -313,6 +313,29 @@ Find more information about how to deal with common errors related to Bitnami
## Upgrading
### To 9.0.0
[On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
**What changes were introduced in this major version?**
- Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
- Move dependency information from the *requirements.yaml* to the *Chart.yaml*
- After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
**Considerations when upgrading to this version**
- If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
- If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
- If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
**Useful links**
- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
- https://helm.sh/docs/topics/v2_v3_migration/
- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
### To 8.0.0
The [Bitnami TestLink](https://github.com/bitnami/bitnami-docker-testlink) image was migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Apache daemon was started as the `daemon` user. From now on, both the container and the Apache daemon run as user `1001`. You can revert this behavior by setting the parameters `containerSecurityContext.runAsUser` to `root`.
@@ -328,7 +351,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
MariaDB dependency version was 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.
### 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.

View File

@@ -1,9 +0,0 @@
dependencies:
- name: mariadb
repository: https://charts.bitnami.com/bitnami
version: 8.0.7
- name: common
repository: https://charts.bitnami.com/bitnami
version: 0.10.0
digest: sha256:59d155210cf6c256013663c328535d5edeb2025fc91d5e7a4e6972598c850d47
generated: "2020-11-08T08:38:25.740651527Z"

View File

@@ -1,10 +0,0 @@
dependencies:
- name: mariadb
version: 8.x.x
repository: https://charts.bitnami.com/bitnami
condition: mariadb.enabled
- name: common
version: 0.x.x
repository: https://charts.bitnami.com/bitnami
tags:
- bitnami-common

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/testlink
tag: 1.9.20-debian-10-r239
tag: 1.9.20-debian-10-r243
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -505,7 +505,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/apache-exporter
tag: 0.8.0-debian-10-r205
tag: 0.8.0-debian-10-r208
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.