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

[bitnami/wordpress] Fix docs to run as root (#2860)

Browse Source 
* [bitnami/wordpress] Fix docs to run as root

* [bitnami/wordpress] Update components versions

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

Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Miguel Ángel Cabrera Miñagorri
2020-06-17 17:24:05 +02:00
committed by GitHub
parent 94fd9d054d
commit 29041cbce9
4 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bitnami/wordpress/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: wordpress
version: 9.3.11
version: 9.3.12
appVersion: 5.4.2
description: Web publishing platform for building blogs and websites.
icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png

2
bitnami/wordpress/README.md
View File

@@ -424,7 +424,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
### To 9.0.0
The [Bitnami WordPress](https://github.com/bitnami/bitnami-docker-wordpress) 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 `securityContext.runAsUser`, and `securityContext.fsGroup` to `root`.
The [Bitnami WordPress](https://github.com/bitnami/bitnami-docker-wordpress) 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 `securityContext.runAsUser`, and `securityContext.fsGroup` to `0`.
Chart labels and Ingress configuration were also adapted to follow the Helm charts best practices.
Consequences:

4
bitnami/wordpress/values-production.yaml
View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/wordpress
tag: 5.4.2-debian-10-r0
tag: 5.4.2-debian-10-r3
## 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
@@ -450,7 +450,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/apache-exporter
tag: 0.8.0-debian-10-r70
tag: 0.8.0-debian-10-r73
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.

4
bitnami/wordpress/values.yaml
View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/wordpress
tag: 5.4.2-debian-10-r0
tag: 5.4.2-debian-10-r3
## 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
@@ -444,7 +444,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/apache-exporter
tag: 0.8.0-debian-10-r70
tag: 0.8.0-debian-10-r73
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.