self-hosted - issue where volumes are created using default values.yaml resulting in issues with builtin's

[taimoorgit]

What

When self-hosted is installed the using a custom values.yaml the volume sizes and secrets are not setup when the statefulsets/deploys are created for minio/mysql/postgres/etc.

This results in the liveness probe for builtin mysql/postgres failing when using the non-default password and the app cannot connect to mysql because the app has the update password saved but the mysql volume was created with the old password.

Workaround

Delete the pvc's that were created and then the statefulsets/deployments that created them.

Solution for k8s 1.27

Change the PersistentVolumeClaim retention

AC

On Kubernetes v1.27 when a user does helm install/helm upgrade the values.yaml file should update the volu