Kustomize Storage Class Rework

[Falconx1000]

I think creating a storage class inside the kustomize template is confusing and unnecessary. Most clusters will have their own storage class already configured. In my case I run a local kubernetes cluster using rook (Ceph) for my storage. IMHO I think it makes more sense to have the storage classes handled separately outside of the kustomize setup and set a default storage class in kustomize. Have an example storage class that can be added if the user wishes to add a new storage class before applying the kustomize. Please let me know what the thoughts are on this. I will be looking to modify the kustomize files to fit my use case and I can create a PR if that change is something that you would like to see.

[c-bordon]

Hello Falconx1000, at the moment we have the repository adapted to be deployed in AWS using the EBS storage class, and locally with microk8s, we consider adding the storage class in kustomize to make it more descriptive. I consider that your contribution is valid, we are going to keep the issue to be included in our backlog and carry out tests and modify if necessary our repository with your contribution.