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>
* 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