mirror of
https://github.com/bitnami/charts.git
synced 2026-03-14 06:47:28 +08:00
[bitnami/wordpress] MAJOR: WordPress image refactor (#6261)
* [major] WordPress image refactor * fix multisite property name * add clarification * Use nip.io redirection * Update bitnami/wordpress/templates/deployment.yaml Co-authored-by: Juan Ariza Toledano <juanariza@vmware.com> * add array support for wordpressPlugins * [bitnami/wordpress] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Juan Ariza Toledano <juanariza@vmware.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
committed by
GitHub
parent
77bda99775
commit
9c53e015fd
@@ -54,7 +54,7 @@ extraDeploy: []
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/wordpress
|
||||
tag: 5.7.1-debian-10-r19
|
||||
tag: 5.7.1-debian-10-r21
|
||||
## 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
|
||||
@@ -131,10 +131,17 @@ 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
|
||||
##
|
||||
wordpressPlugins: none
|
||||
## @param apacheConfiguration The content for your custom httpd.conf file (advanced feature)
|
||||
##
|
||||
apacheConfiguration:
|
||||
## @param existingApacheConfigurationConfigMap The name of an existing secret with your custom wp-config.php file (advanced feature)
|
||||
## @param existingApacheConfigurationConfigMap The name of an existing secret with your custom httpd.conf file (advanced feature)
|
||||
## NOTE: When it's set the `apacheConfiguration` parameter is ignored
|
||||
##
|
||||
existingApacheConfigurationConfigMap:
|
||||
@@ -210,6 +217,20 @@ extraEnvVarsCM:
|
||||
##
|
||||
extraEnvVarsSecret:
|
||||
|
||||
## @section WordPress Multisite Configuration parameters
|
||||
## ref: https://github.com/bitnami/bitnami-docker-wordpress#multisite-configuration
|
||||
|
||||
## @param multisite.enable Whether to enable WordPress Multisite configuration.
|
||||
## @param multisite.host WordPress Multisite hostname/address. This value is mandatory when enabling Multisite mode.
|
||||
## @param multisite.networkType WordPress Multisite network type to enable. Allowed values: `subfolder`, `subdirectory` or `subdomain`.
|
||||
## @param multisite.enableNipIoRedirect Whether to enable IP address redirection to nip.io wildcard DNS. Useful when running on an IP address with subdomain network type.
|
||||
##
|
||||
multisite:
|
||||
enable: false
|
||||
host: ""
|
||||
networkType: subdomain
|
||||
enableNipIoRedirect: false
|
||||
|
||||
## @section WordPress deployment parameters
|
||||
|
||||
## @param replicaCount Number of WordPress replicas to deploy
|
||||
@@ -676,7 +697,7 @@ metrics:
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/apache-exporter
|
||||
tag: 0.8.0-debian-10-r371
|
||||
tag: 0.8.0-debian-10-r372
|
||||
pullPolicy: IfNotPresent
|
||||
## Optionally specify an array of imagePullSecrets.
|
||||
## Secrets must be manually created in the namespace.
|
||||
|
||||
Reference in New Issue
Block a user