[stable/prestashop] Update deployment apiVersion to 'apps/v1' - Mandatory for K8s 1.16 - #17308

…tory for K8s 1.16 (helm#17308)

Signed-off-by: juan131 <juan@bitnami.com>

…tory for K8s 1.16 (helm#17308)

Signed-off-by: juan131 <juan@bitnami.com>
Signed-off-by: Ali Sattari <ali.sattari@gmail.com>

In helm#17308 the `apiVersion` of the deployment resource was
updated to `apps/v1` in tune with the api's deprecated in k8s 1.16. This change however breaks
upgradability of existing prestashop deployments with helm v3 (rc) as described in
helm/helm#6646.

To fix this, we have defined a `prestashop.deployment.apiVersion` helper that returns the new
`apiVersion` only when k8s 1.16 or higher is in use.

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

In helm#17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated in k8s 1.16. This change however breaks
upgradability of existing mariadb deployments with helm v3 (rc) as described in
helm/helm#6646 and also effects any chart that uses the mariadb chart
as a dependency.

To fix this, we have defined a `mariadb.statefulset.apiVersion` helper that returns the new
`apiVersion` only when k8s 1.16 or higher is in use.

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 helm#17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.

In this PR we have bumped the chart major version to signify this and also added the mariadb.statefulset.apiVersion`
helper that returns the correct `apiVersion` to use depending on the k8s version

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 #17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.

In this PR we have bumped the chart major version to signify this and also added the mariadb.statefulset.apiVersion`
helper that returns the correct `apiVersion` to use depending on the k8s version

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 helm#17308 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>

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 helm#17308 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>

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 #17308 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>

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 helm#17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.

In this PR we have bumped the chart major version to signify this and also added the mariadb.statefulset.apiVersion`
helper that returns the correct `apiVersion` to use depending on the k8s version

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 helm#17308 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>

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 helm#17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.

In this PR we have bumped the chart major version to signify this and also added the mariadb.statefulset.apiVersion`
helper that returns the correct `apiVersion` to use depending on the k8s version

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 helm#17308 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>

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 helm#17308 the `apiVersion` of the statefulset resources was
updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.

In this PR we have bumped the chart major version to signify this and also added the mariadb.statefulset.apiVersion`
helper that returns the correct `apiVersion` to use depending on the k8s version

Signed-off-by: Sameer Naik <sameersbn@vmware.com>

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 helm#17308 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>