Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
In https://github.com/helm/charts/pulls/12642 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
This major version signifies this change.
Signed-off-by: Sameer Naik <sameersbn@vmware.com>
* Fixed template reference in tls-secrets.yaml
Template reference was missing `wordpress.` prefix
Signed-off-by: Mike Larah <mike.larah@endjin.com>
* Bump chart version
Signed-off-by: Mike Larah <mike.larah@endjin.com>
* Bump chart version
Signed-off-by: Mike Larah <mike.larah@endjin.com>
* Allow to specify a single hostname
Signed-off-by: Andres Martinez Gotor <andres@bitnami.com>
* Apply changes to values-production
Signed-off-by: Andres Martinez Gotor <andres@bitnami.com>
* Parameterized the target port for https
The use case is when you need to go HTTPS -> ELB -> HTTP -> Wordpress.
Bumped chart version.
Updated readme to include service
Includes annotations for httpsTargetPort
Signed-off-by: Matt Gardner <hi@mattgardner.me>
* Updated documentation and added annotations to values.
Signed-off-by: Matt Gardner <hi@mattgardner.com>
* Updated chart version and removed redundant default value
Signed-off-by: Matt Gardner <hi@mattgardner.com>
This allows the Helm release to be switch between LoadBalancer and ClusterIP with getting the following error:
Service "wordpress" is invalid: [spec.ports[0].nodePort: Forbidden: may not be used when `type` is 'ClusterIP', spec.ports[1].nodePort: Forbidden: may not be used when `type` is 'ClusterIP']
Signed-off-by: adtennant <alex@adtennant.co.uk>
* [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>
* [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
