* [stable/wordpress] Add global 'imagePullSecrets' to overwrite any other existing one
Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
* Fix typo and document variable
Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
* Fix typo in helpers
Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
* [stable/wordpress] Enable configuration of AllowOverride
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Add custom htaccess cm
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Add helper
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Update allowOverride values
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Expose livenessProbe and readinessProbe headers to consumer
**Problem:** Despite docs that say otherwise, Kubernetes treats a 302 HTTP response as "failed" in liveness and readiness probes. When using ingress-terminated HTTPS, it is common for HTTP requests to WordPress to result in 302-redirects to the HTTPS equivalent. As a result, the container is considered unhealthy/unready.
**Solution:** Expose the `httpHeaders` property of the `httpGet` in the probe definition so that consumers can, for example, pass the `X-Forwarded-Proto: https` header to prevent the 302 and instead get a 200 response status. The headers are exposed as optional `livenessProbeHeaders` and `readinessProbeHeaders` arrays, and only included in the deployment definition when defined.
* Update `deployment.yaml` to include optional headers.
* Update `values.yaml` and `values-production.yaml` with commented-out examples.
* Update `README.md` with configuration options, and a more detailed explanation in the Ingress section.
* Update `Chart.yaml` version number from `3.3.0` to `3.3.1`.
Signed-off-by: Jared Reisinger <jaredreisinger@hotmail.com>
* bump version
Signed-off-by: Jared Reisinger <jaredreisinger@hotmail.com>
* bump version
Signed-off-by: Jared Reisinger <jaredreisinger@hotmail.com>
* [stable/wordpress] fix required string value being parsed as bool
Reverts #7101 which breaks ensuring the allowEmptyPassword is always a
string of value "yes" or "no".
* keep allowEmptyPassword Helm value as a boolean
* [stable/wordpress] Add pod tolerations and affinity.
* [stable/wordpress] Document tolerations and affinity in README
* [stable/wordpress] Bump chart version
* bump to 2.1.0
* [stable/wordpress] Remove extra blank lines
* wordpress: update to `bitnami/wordpress:4.7.5-r3`
* wordpress: bump chart version to `0.6.3`
* wordpress: fix probes to properly query pod health
* Rename MARIADB_PORT to MARIADB_PORT_NUMBER
* Allow to the Wordpress helm chart to receive an existing database or create it by itself
* Allow to the Wordpress helm chart to receive an existing database or create it by itself
* added links to documentation for new env vars
* added changes with compatibility threats for 0.4.x chart series. Bumping to 0.5.0
* added defaults for many values and fixes typos
* added defaults for many values and fixes typos
* fix typo
* cosmetic revision
* updated dependency on mariadb chart 0.5.10
* environment vars clean up
* Readme reformatting
* added changes with compatibility threats for 0.4.x chart series. Bumping to 0.5.0
* added defaults for many values and fixes typos
* fix typo
* Allow to the Wordpress helm chart to receive an existing database or create it by itself
* added defaults for many values and fixes typos
* fix typo
* fixing default value in README for AllowEmptyPassword
* wordpress: add alpha and beta storageclass annotation support
* wordpress: use random password if not specified
* wordpress: update MariaDB dep
* wordpress: explicitly set imagePullPolicy
* wordpress: increase resource name truncation and trim '-' suffix
* wordpress: improve storageclass readme description
* wordpress: use built-in toYaml helper
The pod template labels are used as selectors for the deployment, so
they should be the minimal required to uniquely select the
ReplicaSets/Pods. See https://github.com/kubernetes/helm/issues/1390 for
more info about this change.