[bitnami/wordpress-intel] Remove wordpressAutoUpdateLevel parameter in the WordPress for Intel chart (#9769)

* Remove wordpressAutoUpdateLevel parameter in the WordPress for Intel chart

Signed-off-by: Jota Martos <jotamartos@vmware.com>

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

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

* [bitnami/wordpress-intel] Update components versions

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

Co-authored-by: Jota Martos <jotamartos@vmware.com>
Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Juan José Martos
2022-04-12 18:53:58 +02:00
committed by GitHub
parent 11f7608534
commit 746c028097
4 changed files with 21 additions and 21 deletions

View File

@@ -35,4 +35,4 @@ name: wordpress-intel
sources:
- https://github.com/bitnami/bitnami-docker-wordpress-intel
- https://wordpress.org/
version: 0.1.30
version: 0.2.0

View File

@@ -89,14 +89,14 @@ The command removes all the Kubernetes components associated with the chart and
### WordPress Image parameters
| Name | Description | Value |
| ------------------- | ---------------------------------------------------- | --------------------- |
| `image.registry` | WordPress image registry | `docker.io` |
| `image.repository` | WordPress image repository | `bitnami/wordpress` |
| `image.tag` | WordPress image tag (immutable tags are recommended) | `5.8.2-debian-10-r34` |
| `image.pullPolicy` | WordPress image pull policy | `IfNotPresent` |
| `image.pullSecrets` | WordPress image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
| Name | Description | Value |
| ------------------- | ---------------------------------------------------- | ------------------------- |
| `image.registry` | WordPress image registry | `docker.io` |
| `image.repository` | WordPress image repository | `bitnami/wordpress-intel` |
| `image.tag` | WordPress image tag (immutable tags are recommended) | `5.9.3-debian-10-r8` |
| `image.pullPolicy` | WordPress image pull policy | `IfNotPresent` |
| `image.pullSecrets` | WordPress image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
### WordPress Configuration parameters
@@ -117,7 +117,6 @@ The command removes all the Kubernetes components associated with the chart and
| `wordpressConfiguration` | The content for your custom wp-config.php file (advanced feature) | `""` |
| `existingWordPressConfigurationSecret` | The name of an existing secret with your custom wp-config.php file (advanced feature) | `""` |
| `wordpressConfigureCache` | Enable W3 Total Cache plugin and configure cache settings | `false` |
| `wordpressAutoUpdateLevel` | Level of auto-updates to allow. Allowed values: `major`, `minor` or `none`. | `none` |
| `wordpressPlugins` | Array of plugins to install and activate. Can be specified as `all` or `none`. | `none` |
| `customPostInitScripts` | Custom post-init.d user scripts | `{}` |
| `smtpHost` | SMTP server host | `""` |
@@ -238,7 +237,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.enabled` | Enable init container that changes the owner/group of the PV mount point to `runAsUser:fsGroup` | `false` |
| `volumePermissions.image.registry` | Bitnami Shell image registry | `docker.io` |
| `volumePermissions.image.repository` | Bitnami Shell image repository | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `10-debian-10-r280` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `10-debian-10-r392` |
| `volumePermissions.image.pullPolicy` | Bitnami Shell image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Bitnami Shell image pull secrets | `[]` |
| `volumePermissions.resources.limits` | The resources limits for the init container | `{}` |
@@ -268,7 +267,7 @@ The command removes all the Kubernetes components associated with the chart and
| `metrics.port` | NGINX Container Status Port scraped by Prometheus Exporter | `""` |
| `metrics.image.registry` | NGINX Prometheus exporter image registry | `docker.io` |
| `metrics.image.repository` | NGINX Prometheus exporter image repository | `bitnami/nginx-exporter` |
| `metrics.image.tag` | NGINX Prometheus exporter image tag (immutable tags are recommended) | `0.9.0-debian-10-r235` |
| `metrics.image.tag` | NGINX Prometheus exporter image tag (immutable tags are recommended) | `0.10.0-debian-10-r106` |
| `metrics.image.pullPolicy` | NGINX Prometheus exporter image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `metrics.resources.limits` | The resources limits for the Prometheus exporter container | `{}` |
@@ -309,7 +308,7 @@ The command removes all the Kubernetes components associated with the chart and
| Name | Description | Value |
| ------------------------------------------ | ------------------------------------------------------------------------- | ------------------- |
| `mariadb.enabled` : | Deploy a MariaDB server to satisfy the applications database requirements | `true` |
| `mariadb.enabled` | Deploy a MariaDB server to satisfy the applications database requirements | `true` |
| `mariadb.architecture` | MariaDB architecture. Allowed values: `standalone` or `replication` | `standalone` |
| `mariadb.auth.rootPassword` | MariaDB root password | `""` |
| `mariadb.auth.database` | MariaDB custom database | `bitnami_wordpress` |
@@ -448,6 +447,12 @@ As an alternative, use one of the preset configurations for pod affinity, pod an
Find more information about how to deal with common errors related to Bitnami's Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues).
## Notable changes
### 0.2.0
Removed support for limiting auto-updates to WordPress core via the `wordpressAutoUpdateLevel` option. To update WordPress core, we recommend you use the `helm upgrade` command to update your deployment instead of using the built-in update functionality.
## Bitnami Kubernetes Documentation
Bitnami Kubernetes documentation is available at [https://docs.bitnami.com/](https://docs.bitnami.com/). You can find there the following resources:

View File

@@ -155,8 +155,6 @@ spec:
value: {{ .Values.wordpressScheme | quote }}
- name: WORDPRESS_EXTRA_WP_CONFIG_CONTENT
value: {{ .Values.wordpressExtraConfigContent | quote }}
- name: WORDPRESS_AUTO_UPDATE_LEVEL
value: {{ .Values.wordpressAutoUpdateLevel | quote }}
- name: WORDPRESS_PLUGINS
value: {{ join "," .Values.wordpressPlugins | quote }}
- name: NGINX_HTTP_PORT_NUMBER

View File

@@ -69,7 +69,7 @@ diagnosticMode:
image:
registry: docker.io
repository: bitnami/wordpress-intel
tag: 5.9.3-debian-10-r8
tag: 5.9.3-debian-10-r9
## 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
@@ -146,9 +146,6 @@ existingWordPressConfigurationSecret: ""
## NOTE: useful if you deploy Memcached for caching database queries or you use an external cache server
##
wordpressConfigureCache: false
## @param wordpressAutoUpdateLevel Level of auto-updates to allow. Allowed values: `major`, `minor` or `none`.
##
wordpressAutoUpdateLevel: none
## @param wordpressPlugins Array of plugins to install and activate. Can be specified as `all` or `none`.
## NOTE: If set to all, only plugins that are already installed will be activated, and if set to none, no plugins will be activated
##
@@ -623,7 +620,7 @@ volumePermissions:
image:
registry: docker.io
repository: bitnami/bitnami-shell
tag: 10-debian-10-r392
tag: 10-debian-10-r393
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
@@ -699,7 +696,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/nginx-exporter
tag: 0.10.0-debian-10-r106
tag: 0.10.0-debian-10-r107
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.