[bitnami/wordpress] Add support to deploy Memcached for caching database queries (#5849)

2026-03-06 06:58:50 +08:00 · 2021-03-22 15:06:01 +01:00
parent 68cb8c1028
commit 145f5c2a81
11 changed files with 289 additions and 185 deletions
--- a/bitnami/wordpress/Chart.lock
+++ b/bitnami/wordpress/Chart.lock
@@ -2,8 +2,11 @@ dependencies:
 - name: mariadb
  repository: https://charts.bitnami.com/bitnami
  version: 9.3.5
+- name: memcached
+  repository: https://charts.bitnami.com/bitnami
+  version: 5.7.0
 - name: common
  repository: https://charts.bitnami.com/bitnami
  version: 1.4.1
-digest: sha256:3c86816e23c208b792a83b9a8ce8eb7300e8046d109a3cc9d2c174f2ed931170
-generated: "2021-03-09T19:42:06.516002252Z"
+digest: sha256:a618da4389c3f250d05f9f67ca78e79eac5268fc94e05861c425088668ad3c38
+generated: "2021-03-19T12:22:24.254444+01:00"
--- a/bitnami/wordpress/Chart.yaml
+++ b/bitnami/wordpress/Chart.yaml
@@ -7,6 +7,10 @@ dependencies:
    name: mariadb
    repository: https://charts.bitnami.com/bitnami
    version: 9.x.x
+  - condition: memcached.enabled
+    name: memcached
+    repository: https://charts.bitnami.com/bitnami
+    version: 5.x.x
  - name: common
    repository: https://charts.bitnami.com/bitnami
    tags:
@@ -31,4 +35,4 @@ name: wordpress
 sources:
  - https://github.com/bitnami/bitnami-docker-wordpress
  - http://www.wordpress.com/
-version: 10.6.13
+version: 10.7.0
--- a/bitnami/wordpress/README.md
+++ b/bitnami/wordpress/README.md
@@ -13,7 +13,7 @@ $ helm install my-release bitnami/wordpress

 This chart bootstraps a [WordPress](https://github.com/bitnami/bitnami-docker-wordpress) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.

-It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment for the database requirements of the WordPress application.
+It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment for the database requirements of the WordPress application, and the [Bitnami Memcached chart](https://github.com/bitnami/charts/tree/master/bitnami/memcached) that can be used to cache database queries.

 Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the [BKPR](https://kubeprod.io/).

@@ -180,7 +180,7 @@ The following table lists the configurable parameters of the WordPress chart and
 | `persistence.enabled`       | Enable persistence using PVC             | `true`                                      |
 | `persistence.existingClaim` | Enable persistence using an existing PVC | `nil`                                       |
 | `persistence.storageClass`  | PVC Storage Class                        | `nil` (uses alpha storage class annotation) |
-| `persistence.accessMode`    | PVC Access Mode                          | `ReadWriteOnce`                             |
+| `persistence.accessModes`   | PVC Access Modes                        | `[ReadWriteOnce]`                            |
 | `persistence.size`          | PVC Storage Request                      | `10Gi`                                      |
 | `persistence.dataSource`    | PVC data source                          | `{}`                                        |

@@ -203,6 +203,7 @@ The following table lists the configurable parameters of the WordPress chart and
 | `externalDatabase.database`               | Name of the existing database                        | `bitnami_wordpress`                            |
 | `externalDatabase.port`                   | Database port number                                 | `3306`                                         |
 | `externalDatabase.existingSecret`         | Name of the database existing Secret Object          | `nil`                                          |
+| `memcached.enabled`                       | Deploy Memcached for caching database queries        | `false`                                        |

 ### Volume Permissions parameters

@@ -298,23 +299,6 @@ kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath=
 kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[2].metadata.name}') -c wordpress -- wp maintenance-mode activate
 ```

-### Additional environment variables
-
-In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `extraEnvVars` property.
-
-```yaml
-wordpress:
-  extraEnvVars:
-    - name: LOG_LEVEL
-      value: error
-```
-
-Alternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.
-
-### Sidecars
-
-If additional containers are needed in the same pod as WordPress (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter. If these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter. [Learn more about configuring and using sidecar containers](https://docs.bitnami.com/kubernetes/apps/wordpress/administration/configure-use-sidecars/).
-
 ### External database support

 You may want to have WordPress connect to an external database rather than installing one inside your cluster. Typical reasons for this are to use a managed database service, or to share a common database server for all your applications. To achieve this, the chart allows you to specify credentials for an external database with the [`externalDatabase` parameter](#parameters). You should also disable the MariaDB installation with the `mariadb.enabled` option. Here is an example:
@@ -330,11 +314,11 @@ externalDatabase.port=3306

 Refer to the [documentation on using an external database with WordPress](https://docs.bitnami.com/kubernetes/apps/wordpress/configuration/use-external-database/) and the [tutorial on integrating WordPress with a managed cloud database](https://docs.bitnami.com/tutorials/secure-wordpress-kubernetes-managed-database-ssl-upgrades/) for more information.

-### Pod affinity
+### Memcached

-This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
+This chart provides support for using Memcached to cache database queries improving the website performance. To enable this feature, set `memcached.enabled` to `true`.

-As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
+When this features is enabled, a Memcached server will be deployed in your K8s cluster using the Bitnami Memcached chart and the [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/) plugin will be activated and configured to use the Memcached server for database caching.

 ### Ingress

@@ -358,6 +342,29 @@ By default, the container image includes all the default `.htaccess` files in Wo

 The [Bitnami WordPress](https://github.com/bitnami/bitnami-docker-wordpress) image stores the WordPress data and configurations at the `/bitnami` path of the container. Persistent Volume Claims are used to keep the data across deployments. [Learn more about persistence in the chart documentation](https://docs.bitnami.com/kubernetes/apps/wordpress/configuration/chart-persistence/).

+### Additional environment variables
+
+In case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `extraEnvVars` property.
+
+```yaml
+wordpress:
+  extraEnvVars:
+    - name: LOG_LEVEL
+      value: error
+```
+
+Alternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.
+
+### Sidecars
+
+If additional containers are needed in the same pod as WordPress (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter. If these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter. [Learn more about configuring and using sidecar containers](https://docs.bitnami.com/kubernetes/apps/wordpress/administration/configure-use-sidecars/).
+
+### Pod affinity
+
+This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
+
+As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
+
 ## Troubleshooting

 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).
--- a/bitnami/wordpress/ci/values-memcached.yaml
+++ b/bitnami/wordpress/ci/values-memcached.yaml
@@ -0,0 +1,2 @@
+memcached:
+  enabled: true
--- a/bitnami/wordpress/templates/_helpers.tpl
+++ b/bitnami/wordpress/templates/_helpers.tpl
@@ -8,6 +8,14 @@ We truncate at 63 chars because some Kubernetes name fields are limited to this
 {{- printf "%s-%s" .Release.Name "mariadb" | trunc 63 | trimSuffix "-" -}}
 {{- end -}}

+{{/*
+Create a default fully qualified app name.
+We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
+*/}}
+{{- define "wordpress.memcached.fullname" -}}
+{{- printf "%s-%s" .Release.Name "memcached" | trunc 63 | trimSuffix "-" -}}
+{{- end -}}
+
 {{/*
 Return the proper WordPress image name
 */}}
--- a/bitnami/wordpress/templates/configmap.yaml
+++ b/bitnami/wordpress/templates/configmap.yaml
@@ -1,8 +0,0 @@
-{{- if .Values.customPostInitScripts }}
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: {{ include "common.names.fullname" . }}-postinit
-data:
-{{- include "common.tplvalues.render" (dict "value" .Values.customPostInitScripts "context" $) | nindent 2 }}
-{{- end }}
--- a/bitnami/wordpress/templates/deployment.yaml
+++ b/bitnami/wordpress/templates/deployment.yaml
@@ -212,7 +212,7 @@ spec:
            - mountPath: /htaccess
              name: custom-htaccess
            {{- end }}
-            {{- if .Values.customPostInitScripts }}
+            {{- if or .Values.customPostInitScripts .Values.memcached.enabled }}
            - mountPath: /docker-entrypoint-init.d
              name: custom-postinit
            {{- end }}
@@ -258,10 +258,10 @@ spec:
              - key: wordpress-htaccess.conf
                path: wordpress-htaccess.conf
        {{- end }}
-        {{- if .Values.customPostInitScripts }}
+        {{- if or .Values.customPostInitScripts .Values.memcached.enabled }}
        - name: custom-postinit
          configMap:
-            name: {{ include "common.names.fullname" . }}-postinit
+            name: {{ printf "%s-postinit" (include "common.names.fullname" .) }}
            defaultMode: 0755
        {{- end }}
        - name: wordpress-data
--- a/bitnami/wordpress/templates/postinit-configmap.yaml
+++ b/bitnami/wordpress/templates/postinit-configmap.yaml
@@ -0,0 +1,35 @@
+{{- if or .Values.customPostInitScripts .Values.memcached.enabled }}
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: {{ printf "%s-postinit" (include "common.names.fullname" .) }}
+data:
+  {{- if .Values.memcached.enabled }}
+  {{- $memcachedFullname := include "wordpress.memcached.fullname" . }}
+  {{- $memcachedPort := int .Values.memcached.service.port }}
+  {{- $releaseNamespace := .Release.Namespace }}
+  {{- $clusterDomain := .Values.clusterDomain }}
+  00-configure-w3-total-cache.sh: |-
+    #!/bin/bash
+
+    # Add permisions to edit wp-config.php
+    chmod +w /bitnami/wordpress/wp-config.php
+
+    # Activate W3 Total Cache pairs
+    wp plugin activate w3-total-cache
+    wp total-cache fix_environment
+
+    # Choose 'Memcached' as database cache method
+    wp total-cache option set dbcache.engine memcached --type=string
+    wp total-cache flush all
+    wp total-cache option set dbcache.memcached.servers {{ $memcachedFullname }}.{{ $releaseNamespace }}.svc.{{ $clusterDomain }}:{{ $memcachedPort }} --type=string
+    wp total-cache option set dbcache.enabled true --type=boolean
+    wp total-cache flush all
+
+    # Revoke permisions to edit wp-config.php
+    chmod -w bitnami/wordpress/wp-config.php
+  {{- end }}
+  {{- if .Values.customPostInitScripts }}
+  {{- include "common.tplvalues.render" (dict "value" .Values.customPostInitScripts "context" $) | nindent 2 }}
+  {{- end }}
+{{- end }}
--- a/bitnami/wordpress/templates/pvc.yaml
+++ b/bitnami/wordpress/templates/pvc.yaml
@@ -12,7 +12,13 @@ metadata:
  {{- end }}
 spec:
  accessModes:
+  {{- if not (empty .Values.persistence.accessModes) }}
+  {{- range .Values.persistence.accessModes }}
+    - {{ . | quote }}
+  {{- end }}
+  {{- else }}
    - {{ .Values.persistence.accessMode | quote }}
+  {{- end }}
  resources:
    requests:
      storage: {{ .Values.persistence.size | quote }}
--- a/bitnami/wordpress/templates/tls-secrets.yaml
+++ b/bitnami/wordpress/templates/tls-secrets.yaml
@@ -19,7 +19,8 @@ data:
  tls.key: {{ .key | b64enc }}
 ---
 {{- end }}
-{{- else if and .Values.ingress.tls (not .Values.ingress.certManager) }}
+{{- end }}
+{{- if and .Values.ingress.tls (not .Values.ingress.certManager) }}
 {{- $ca := genCA "wordpress-ca" 365 }}
 {{- $cert := genSignedCert .Values.ingress.hostname nil (list .Values.ingress.hostname) 365 $ca }}
 apiVersion: v1
--- a/bitnami/wordpress/values.yaml
+++ b/bitnami/wordpress/values.yaml
@@ -23,22 +23,20 @@ image:
  ## Optionally specify an array of imagePullSecrets.
  ## Secrets must be manually created in the namespace.
  ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
+  ## e.g:
+  ## pullSecrets:
+  ##   - myRegistryKeySecretName
  ##
-  # pullSecrets:
-  #   - myRegistryKeySecretName
+  pullSecrets: []
  ## Set to true if you would like to see extra information on logs
  ##
  debug: false

-## Force target Kubernetes version (using Helm capabilites if not set)
-##
-kubeVersion:
-
-## String to partially override aspnet-core.fullname template (will maintain the release name)
+## String to partially override common.names.fullname template (will maintain the release name)
 ##
 # nameOverride:

-## String to fully override aspnet-core.fullname template
+## String to fully override common.names.fullname template
 ##
 # fullnameOverride:

@@ -50,19 +48,14 @@ commonLabels: {}
 ##
 commonAnnotations: {}

+## Force target Kubernetes version (using Helm capabilites if not set)
+##
+kubeVersion:
+
 ## Kubernetes Cluster Domain
 ##
 clusterDomain: cluster.local

-## Deployment pod host aliases
-## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
-##
-hostAliases:
-  # Necessary for apache-exporter to work
-  - ip: "127.0.0.1"
-    hostnames:
-      - "status.localhost"
-
 ## Extra objects to deploy (value evaluated as a template)
 ##
 extraDeploy: []
@@ -71,34 +64,34 @@ extraDeploy: []
 ##
 serviceAccountName: default

-## User of the application
+## WordPress username
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
 wordpressUsername: user

-## Application password
+## WordPress user password
 ## Defaults to a random 10-character alphanumeric string if not set
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
-# wordpressPassword:
+wordpressPassword: ""

 ## Use existing secret (does not create the WordPress Secret object)
-## Must contain key `wordpress-secret`
+## NOTE: Must contain key `wordpress-password`
 ## NOTE: When it's set, the `wordpressPassword` parameter is ignored
 ##
 # existingSecret:

-## Admin email
+## WordPress user email
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
 wordpressEmail: user@example.com

-## First name
+## WordPress user first name
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
 wordpressFirstName: FirstName

-## Last name
+## WordPress user last name
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
 wordpressLastName: LastName
@@ -118,56 +111,39 @@ wordpressTablePrefix: wp_
 ##
 wordpressScheme: http

-## Skip wizard installation (only if you use an external database that already contains WordPress data)
+## Skip wizard installation (recommended if you use an external database that already contains WordPress data)
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress#connect-wordpress-docker-container-to-an-existing-database
 ##
 wordpressSkipInstall: false

 ## Add extra content to the default configuration file
+## e.g:
+## wordpressExtraConfigContent: |
+##   @ini_set( 'post_max_size', '128M');
+##   @ini_set( 'memory_limit', '256M' );
 ##
 wordpressExtraConfigContent: ""

-## Set to `false` to allow the container to be started with blank passwords
-## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
+## Make use of custom post-init.d user scripts functionality inside the bitnami/wordpress image
+## ref: https://github.com/bitnami/bitnami-docker-wordpress/tree/master/5/debian-10/rootfs/post-init.d
 ##
-allowEmptyPassword: true
-
-## Set Apache allowOverride to None
-## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
+## The logic of the post-init.d user scripts is that all is all files with extensions .sh, .sql or .php are executed for one time only, at the very first initialization of the pod as the very last step of entrypoint.sh.
+## e.g:
+## customPostInitScripts:
+##   enable-multisite.sh: |
+##     #!/bin/bash
+##     chmod +w /bitnami/wordpress/wp-config.php
+##     wp core multisite-install --url=example.com --title="Welcome to the WordPress Multisite" --admin_user="doesntmatternotreallyused" --admin_password="doesntmatternotreallyused" --admin_email="user@example.com"
+##     cat /docker-entrypoint-init.d/.htaccess > /bitnami/wordpress/.htaccess
+##     chmod -w bitnami/wordpress/wp-config.php
+##   .htaccess: |
+##     RewriteEngine On
+##     RewriteBase /
+##     ...
 ##
-allowOverrideNone: false
-
-## Persist the custom changes of the htaccess. It depends on the value of
-## `.Values.allowOverrideNone`, when `yes` it will persist `/opt/bitnami/wordpress/wordpress-htaccess.conf`
-## if `no` it will persist `/opt/bitnami/wordpress/.htaccess`
+## NOTE: Combined with extraVolume and extraVolumeMounts to mount the configmap to /docker-entrypoint-init.d where custom user init scripts are looked for
 ##
-htaccessPersistenceEnabled: false
-
-## ConfigMap with custom wordpress-htaccess.conf file (requires allowOverrideNone to true)
-##
-customHTAccessCM:
-
-## Command and args for running the container (set to default if not set). Use array form
-##
-command: []
-args: []
-
-## Set up update strategy for wordpress installation. Set to Recreate if you use persistent volume that cannot be mounted by more than one pods to makesure the pods is destroyed first.
-## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
-## Example:
-## updateStrategy:
-##  type: RollingUpdate
-##  rollingUpdate:
-##    maxSurge: 25%
-##    maxUnavailable: 25%
-##
-updateStrategy:
-  type: RollingUpdate
-
-## Use an alternate scheduler, e.g. "stork".
-## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
-##
-# schedulerName:
+customPostInitScripts: {}

 ## SMTP mail delivery configuration
 ## ref: https://github.com/bitnami/bitnami-docker-wordpress/#smtp-configuration
@@ -185,12 +161,33 @@ updateStrategy:
 ##
 # smtpExistingSecret:

-## Number of replicas (requires ReadWriteMany PVC support)
+## Set to `false` to allow the container to be started with blank passwords
+## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
 ##
-replicaCount: 1
+allowEmptyPassword: true
+
+## Set Apache allowOverride to None
+## ref: https://github.com/bitnami/bitnami-docker-wordpress#environment-variables
+##
+allowOverrideNone: false
+
+## Persist the custom changes of the htaccess.
+## If `allowOverrideNone` is `true`, it will persist `/opt/bitnami/wordpress/wordpress-htaccess.conf`
+## If `allowOverrideNone` is `false`, it will persist `/opt/bitnami/wordpress/.htaccess`
+##
+htaccessPersistenceEnabled: false
+
+## Existing ConfigMap with containing a custom wordpress-htaccess.conf file (requires `allowOverrideNone=true`)
+##
+customHTAccessCM: ""
+
+## Command and args for running the container (set to default if not set). Use array form
+##
+command: []
+args: []

 ## An array to add extra env vars
-## Example:
+## e.g:
 ## extraEnvVars:
 ##   - name: FOO
 ##     value: "bar"
@@ -205,6 +202,36 @@ extraEnvVarsCM:
 ##
 extraEnvVarsSecret:

+## Number of replicas (requires ReadWriteMany PVC support)
+##
+replicaCount: 1
+
+## Set up update strategy for wordpress installation. Set to Recreate if you use persistent volume that cannot be mounted by more than one pods to makesure the pods is destroyed first.
+## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
+## e.g:
+## updateStrategy:
+##  type: RollingUpdate
+##  rollingUpdate:
+##    maxSurge: 25%
+##    maxUnavailable: 25%
+##
+updateStrategy:
+  type: RollingUpdate
+
+## Use an alternate scheduler, e.g. "stork".
+## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
+##
+# schedulerName:
+
+## WordPress pod host aliases
+## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
+##
+hostAliases:
+  ## Required for apache-exporter to work
+  - ip: "127.0.0.1"
+    hostnames:
+      - "status.localhost"
+
 ## Extra volumes to add to the deployment
 ##
 extraVolumes: []
@@ -214,7 +241,7 @@ extraVolumes: []
 extraVolumeMounts: []

 ## Add sidecars to the pod.
-## Example:
+## e.g:
 ## sidecars:
 ##   - name: your-image-name
 ##     image: your-image
@@ -227,7 +254,7 @@ sidecars: {}

 ## Add init containers to the pod.
 ## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
-## Example:
+## e.g:
 ## initContainers:
 ##  - name: your-image-name
 ##    image: your-image
@@ -376,10 +403,12 @@ containerPorts:
  http: 8080
  https: 8443

-## Kubernetes configuration
-## For minikube, set this to NodePort, elsewhere use LoadBalancer or ClusterIP
+## WordPress Service properties
 ##
 service:
+  ## WordPress Service type
+  ## For minikube, set this to NodePort, elsewhere use LoadBalancer or ClusterIP
+  ##
  type: LoadBalancer
  ## HTTP Port
  ##
@@ -400,7 +429,7 @@ service:
  nodePorts:
    http: ""
    https: ""
-  ## Service clusterIP.
+  ## Service clusterIP
  ##
  # clusterIP: None
  ## loadBalancerIP for the SuiteCRM Service (optional, cloud specific)
@@ -409,7 +438,7 @@ service:
  # loadBalancerIP:
  ## Load Balancer sources
  ## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
-  ## Example:
+  ## e.g:
  ## loadBalancerSourceRanges:
  ##   - 10.10.10.0/24
  ##
@@ -471,10 +500,12 @@ ingress:

  ## The list of additional hostnames to be covered with this ingress record.
  ## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
+  ## e.g:
  ## extraHosts:
-  ## - name: wordpress.local
-  ##   path: /
+  ##   - name: wordpress.local
+  ##     path: /
  ##
+  extraHosts: []

  ## Any additional arbitrary paths that may need to be added to the ingress under the main host.
  ## For example: The ALB ingress controller requires a special rule for handling SSL redirection.
@@ -484,35 +515,41 @@ ingress:
  ##     serviceName: ssl-redirect
  ##     servicePort: use-annotation
  ##
+  extraPaths: []

  ## The tls configuration for additional hostnames to be covered with this ingress record.
  ## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
+  ## e.g:
  ## extraTls:
  ## - hosts:
  ##     - wordpress.local
  ##   secretName: wordpress.local-tls
  ##
+  extraTls: []

  ## If you're providing your own certificates, please use this to add the certificates as secrets
-  ## key and certificate should start with -----BEGIN CERTIFICATE----- or
-  ## -----BEGIN RSA PRIVATE KEY-----
-  ##
-  ## name should line up with a tlsSecret set further up
-  ## If you're using cert-manager, this is unneeded, as it will create the secret for you if it is not set
+  ## key and certificate are expected in PEM format
+  ## name should line up with a secretName set further up
  ##
+  ## If it is not set and you're using cert-manager, this is unneeded, as it will create a secret for you with valid certificates
+  ## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days
  ## It is also possible to create and manage the certificates outside of this helm chart
  ## Please see README.md for more information
  ##
-  secrets: []
-  ## - name: wordpress.local-tls
-  ##   key:
-  ##   certificate:
+  ## Example
+  ## secrets:
+  ##   - name: wordpress.local-tls
+  ##     key: ""
+  ##     certificate: ""
  ##
+  secrets: []

 ## Enable persistence using Persistent Volume Claims
 ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/
 ##
 persistence:
+  ## If true, use a Persistent Volume Claim, If false, use emptyDir
+  ##
  enabled: true
  ## wordpress data Persistent Volume Storage Class
  ## If defined, storageClassName: <storageClass>
@@ -522,15 +559,67 @@ persistence:
  ##   GKE, AWS & OpenStack)
  ##
  # storageClass: "-"
+  ## Persistent Volume Access Modes
  ##
-  ## If you want to reuse an existing claim, you can pass the name of the PVC using
-  ## the existingClaim variable
-  # existingClaim: your-claim
+  accessModes:
+    - ReadWriteOnce
+  ## DEPRECATED: use `persistence.accessModes` instead
  accessMode: ReadWriteOnce
+  ## Persistent Volume size
+  ##
  size: 10Gi
  ## Custom dataSource
  ##
  dataSource: {}
+  ## Enable persistence using an existing PVC
+  ##
+  # existingClaim:
+
+## Init containers parameters:
+## volumePermissions: Change the owner and group of the persistent volume mount point to runAsUser:fsGroup values
+## based on the podSecurityContext/containerSecurityContext parameters
+##
+volumePermissions:
+  enabled: false
+  image:
+    registry: docker.io
+    repository: bitnami/bitnami-shell
+    tag: "10"
+    pullPolicy: Always
+    ## Optionally specify an array of imagePullSecrets.
+    ## Secrets must be manually created in the namespace.
+    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
+    ## e.g:
+    ## pullSecrets:
+    ##   - myRegistryKeySecretName
+    ##
+    pullSecrets: []
+  ## Init container' resource requests and limits
+  ## ref: http://kubernetes.io/docs/user-guide/compute-resources/
+  ##
+  resources:
+    ## We usually recommend not to specify default resources and to leave this as a conscious
+    ## choice for the user. This also increases chances charts run on environments with little
+    ## resources, such as Minikube. If you do want to specify resources, uncomment the following
+    ## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+    ## e.g:
+    ## limits:
+    ##   cpu: 500m
+    ##   memory: 1Gi
+    ##
+    limits: {}
+    requests: {}
+  ## Init container Security Context
+  ## Note: the chown of the data folder is done to containerSecurityContext.runAsUser
+  ## and not the below volumePermissions.securityContext.runAsUser
+  ## When runAsUser is set to special value "auto", init container will try to chwon the
+  ## data folder to autodetermined user&group, using commands: `id -u`:`id -G | cut -d" " -f2`
+  ## "auto" is especially useful for OpenShift which has scc with dynamic userids (and 0 is not allowed).
+  ## You may want to use this volumePermissions.securityContext.runAsUser="auto" in combination with
+  ## podSecurityContext.enabled=false,containerSecurityContext.enabled=false
+  ##
+  securityContext:
+    runAsUser: 0

 ## Wordpress Pod Disruption Budget configuration
 ## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
@@ -565,9 +654,11 @@ metrics:
    ## Optionally specify an array of imagePullSecrets.
    ## Secrets must be manually created in the namespace.
    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
+    ## e.g:
+    ## pullSecrets:
+    ##   - myRegistryKeySecretName
    ##
-    # pullSecrets:
-    #   - myRegistryKeySecretName
+    pullSecrets: []

  ## Prometheus expoter service parameters
  ##
@@ -597,13 +688,16 @@ metrics:
    ##
    enabled: false
    ## Specify the namespace in which the serviceMonitor resource will be created
+    ##
    # namespace: ""
    ## Specify the interval at which metrics should be scraped
    ##
    interval: 30s
    ## Specify the timeout after which the scrape is ended
+    ##
    # scrapeTimeout: 30s
    ## Specify Metric Relabellings to add to the scrape endpoint
+    ##
    # relabellings:
    ## Specify honorLabels parameter to add the scrape endpoint
    ##
@@ -615,8 +709,7 @@ metrics:

 ##
 ## MariaDB chart configuration
-##
-## https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
+## ref: https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
 ##
 mariadb:
  ## Whether to deploy a mariadb server to satisfy the applications database requirements. To use an external database set this to false and configure the externalDatabase parameters
@@ -684,64 +777,17 @@ externalDatabase:
  ##
  # existingSecret:

-## Make use of custom post-init.d user scripts functionality inside the bitnami/wordpress image
-## ref: https://github.com/bitnami/bitnami-docker-wordpress/tree/master/5/debian-10/rootfs/post-init.d
 ##
-## The logic of the post-init.d user scripts is that all is all files with extensions .sh, .sql or .php are executed for one time only, at the very first initialization of the pod as the very last step of entrypoint.sh.
-## Example:
-## customPostInitScripts:
-##   enable-multisite.sh: |
-##     #!/bin/bash
-##     chmod +w /bitnami/wordpress/wp-config.php
-##     wp core multisite-install --url=example.com --title="Welcome to the WordPress Multisite" --admin_user="doesntmatternotreallyused" --admin_password="doesntmatternotreallyused" --admin_email="user@example.com"
-##     cat /docker-entrypoint-init.d/.htaccess > /bitnami/wordpress/.htaccess
-##     chmod -w bitnami/wordpress/wp-config.php
-##   .htaccess: |
-##     RewriteEngine On
-##     RewriteBase /
-##     ...
+## Memcached chart configuration
+## ref: https://github.com/bitnami/charts/blob/master/bitnami/memcached/values.yaml
 ##
-## NOTE: Combined with extraVolume and extraVolumeMounts to mount the configmap to /docker-entrypoint-init.d where custom user init scripts are looked for
-##
-customPostInitScripts: {}
-
-##
-## Init containers parameters:
-## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup
-##
-volumePermissions:
-  enabled: false
-  image:
-    registry: docker.io
-    repository: bitnami/bitnami-shell
-    tag: "10"
-    pullPolicy: Always
-    ## Optionally specify an array of imagePullSecrets.
-    ## Secrets must be manually created in the namespace.
-    ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
-    ##
-    # pullSecrets:
-    #   - myRegistryKeySecretName
-  resources:
-    # We usually recommend not to specify default resources and to leave this as a conscious
-    # choice for the user. This also increases chances charts run on environments with little
-    # resources, such as Minikube. If you do want to specify resources, uncomment the following
-    # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
-    limits: {}
-    #   cpu: 100m
-    #   memory: 128Mi
-    requests: {}
-    #   cpu: 100m
-    #   memory: 128Mi
-
-  ## Init container Security Context
-  ## Note: the chown of the data folder is done to containerSecurityContext.runAsUser
-  ## and not the below volumePermissions.securityContext.runAsUser
-  ## When runAsUser is set to special value "auto", init container will try to chwon the
-  ## data folder to autodetermined user&group, using commands: `id -u`:`id -G | cut -d" " -f2`
-  ## "auto" is especially useful for OpenShift which has scc with dynamic userids (and 0 is not allowed).
-  ## You may want to use this volumePermissions.securityContext.runAsUser="auto" in combination with
-  ## podSecurityContext.enabled=false,containerSecurityContext.enabled=false
+memcached:
+  ## Whether to deploy a memcached server for caching database queries
  ##
-  securityContext:
-    runAsUser: 0
+  enabled: false
+  ## Service parameters
+  ##
+  service:
+    ## Memcached port
+    ##
+    port: 11211