mirror of
https://github.com/helm/charts.git
synced 2026-08-23 14:27:18 +00:00
Jared ReisingerandKubernetes Prow Robot
d2cd36b0c4
* 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>
21 lines
439 B
YAML
21 lines
439 B
YAML
name: wordpress
|
|
version: 5.0.4
|
|
appVersion: 5.0.2
|
|
description: Web publishing platform for building blogs and websites.
|
|
icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png
|
|
keywords:
|
|
- wordpress
|
|
- cms
|
|
- blog
|
|
- http
|
|
- web
|
|
- application
|
|
- php
|
|
home: http://www.wordpress.com/
|
|
sources:
|
|
- https://github.com/bitnami/bitnami-docker-wordpress
|
|
maintainers:
|
|
- name: Bitnami
|
|
email: containers@bitnami.com
|
|
engine: gotpl
|