Allow use allowedTopologies with helm

[andrejzverev]

Describe the problem/challenge you have
It's not possible to use allowedTopologies in scope of helm chart, since hostpath-class.yaml template know nothing about it. In my understanding allowedTopologies it's an only way to declare which nodes must be used for StorageClass.

Describe the solution you'd like
Implement template support for .Values.hostpathClass.allowedTopologies.

Anything else you would like to add:
Nope

Environment:

• OpenEBS version (use kubectl get po -n openebs --show-labels):
  openebs-localpv-localpv-provisioner-7c97888c7b-mppwd 1/1 Running 0 37m app=localpv-provisioner,chart=localpv-provisioner-4.2.0,component=localpv-provisioner,heritage=Helm,name=openebs-localpv-provisioner,openebs.io/component-name=openebs-localpv-provisioner,pod-template-hash=7c97888c7b,release=openebs-localpv
• Kubernetes version (use kubectl version):
  Client Version: v1.30.12
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.30.10
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• kernel (e.g: uname -a):
• others:

[Abhinandan-Purkait]

@niladrih Is this not supported today?

[niladrih]

It's not possible to set the allowedTopologies field for the default storageClass via the helm values. No harm in having it in there. We could add it in.