* [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>
* [stable/wordpress] Add service annotations
Signed-off-by: Andrejs Volkovs <clalbus@gmail.com>
* [stable/wordpress] Bump version to 5.1.0
Signed-off-by: Andrejs Volkovs <clalbus@gmail.com>
* [stable/wordpress] Initialize service annotations in prod values
Signed-off-by: Andrejs Volkovs <clalbus@gmail.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] Add service.port in values.yaml
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Update NOTES.txt
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* Remove - in template
Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
* [stable/wordpress] Simplify ingress configuration when for cert-manager
Signed-off-by: juan131 <juan@bitnami.com>
* Apply changes on 'values-production.yaml' too
Signed-off-by: juan131 <juan@bitnami.com>
When set to `Local`, we discovered that on OKE, Oracle's LoadBalancer tries route
to nodes where the Pod isn't running and as a result it doesn't work. Change the
default value to `Cluster` seems to be the sane default value we should use.
* [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
* production configuration (optional)
* improved the command description
* bumped chart version
* addressed sameers comments
* changes suggested in review to make clear that you have to download the values-prod file
* updated readme
* Update Chart.yaml
Add version for wordpress
* Typo fix in wordpress/README.md
1. to service your wordpress application ->to the service of your wordpress application
2. WordPress Image->WordPress image keep same format in a table.
3. helm->Helm It's a proper noun
* Update wordpress/README.md
Update wordpress/README.md
* [stable/wordpress] removes unused `externalDatabase.rootPassword` param
* [stable/wordpress] set default value of `externalDatabase.password` to empty string
avoid template rendering errors when no password is required
* [stable/wordpress] bump chart version to 0.8.8
* Adjusting ingress record to better support TLS
* Adjusting indentation per linting
* Adjusting indentation per linting - including stuff not part of original PR
* Adjusting indentation per linting - including stuff not part of original PR
* Bumping to 0.7.0 because ingress change _is_ added functionality but backward compatible
* Documenting option in README.md
* Refactored ingress section, chart is compatible with older chart's ingress section
* Updating values.yaml per linting
* correcting hostnames -> hosts
* $ is available everywhere
* Fixing indentation, allowing certificates to be b64 encoded
* Fixing english
* Updating documentation to give more information about ingress, TLS and TLS secrets
* Fixing typos
* Fixing typos / wording
* fixing capitalizations
