[bitnami/gitea] Release 0.1.4 (#14284)

* [bitnami/gitea] Release 0.1.4 updating components versions

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

* Update README.md with readme-generator-for-helm

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

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-01-11 12:58:55 +01:00
committed by GitHub
parent afafafa0f6
commit 126c1ea339
4 changed files with 8 additions and 8 deletions
+3 -3
View File
@@ -1,9 +1,9 @@
dependencies:
- name: postgresql
repository: https://charts.bitnami.com/bitnami
version: 12.1.6
version: 12.1.9
- name: common
repository: https://charts.bitnami.com/bitnami
version: 2.2.2
digest: sha256:f48cad39d43e57b0fc0e3da24e908f2c6f65645f10f4c1ef8ee992a70d966667
generated: "2022-12-22T01:46:30.982412325Z"
digest: sha256:e19fbf08237c64231e674ad3a2f7c210cdc0d5846c06ec73e023929d3562654a
generated: "2023-01-11T11:23:21.786895144Z"
+1 -1
View File
@@ -30,4 +30,4 @@ name: gitea
sources:
- https://github.com/bitnami/containers/tree/main/bitnami/gitea
- https://gitea.io/
version: 0.1.3
version: 0.1.4
+2 -2
View File
@@ -82,7 +82,7 @@ The command removes all the Kubernetes components associated with the chart and
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------- |
| `image.registry` | Gitea image registry | `docker.io` |
| `image.repository` | Gitea Image name | `bitnami/gitea` |
| `image.tag` | Gitea Image tag | `1.18.0-debian-11-r0` |
| `image.tag` | Gitea Image tag | `1.18.0-debian-11-r5` |
| `image.digest` | Gitea image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `image.pullPolicy` | Gitea image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
@@ -239,7 +239,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.enabled` | Enable init container that changes volume permissions in the data directory (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `11-debian-11-r66` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `11-debian-11-r70` |
| `volumePermissions.image.digest` | Init container volume-permissions image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
+2 -2
View File
@@ -59,7 +59,7 @@ extraDeploy: []
image:
registry: docker.io
repository: bitnami/gitea
tag: 1.18.0-debian-11-r0
tag: 1.18.0-debian-11-r5
digest: ""
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -635,7 +635,7 @@ volumePermissions:
image:
registry: docker.io
repository: bitnami/bitnami-shell
tag: 11-debian-11-r66
tag: 11-debian-11-r70
digest: ""
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.