Hi 

We installed solr operator and then solr using helm package. We are using 
solr-operator version 0.7.0 and solr version 8.11. Solr is working fine.

Our requirement is we need to use Azure File share for PV mount instead of 
dynamic volume. Currently we can see 3 dynamic volumes are created. Each pod is 
creating its own dynamic volume.


PV:
NAME                                       CAPACITY   ACCESS MODES   RECLAIM 
POLICY   STATUS   CLAIM                                                   
STORAGECLASS             AGE
pvc-6b019f0f-f816-41bf-84ac-51d3c4136ff7   20Gi       RWO            Delete     
      Bound    solr-operator/example-solr-secret-example-solrcloud-0   
azurefile-csi            41h
pvc-7702b17a-d017-4425-98b0-2c2ed76561bc   20Gi       RWO            Delete     
      Bound    solr-operator/data-example-solrcloud-zookeeper-1        default  
                6h46m
pvc-87bff553-fdc8-46c6-9d2e-44c6758539e9   20Gi       RWO            Delete     
      Bound    solr-operator/data-example-solrcloud-zookeeper-2        default  
                6h45m
pvc-97f51f09-e08e-46a4-86c5-ba52263dbea2   20Gi       RWO            Delete     
      Bound    solr-operator/example-solr-secret-example-solrcloud-1   
azurefile-csi            41h
pvc-a5e996b0-e986-4574-8ad6-50bca74fbb9b   20Gi       RWO            Delete     
      Bound    solr-operator/data-example-solrcloud-zookeeper-0        default  
                6h47m
pvc-fe1db5e9-dd09-4c97-8383-c2247a094a74   20Gi       RWO            Delete     
      Bound    solr-operator/example-solr-secret-example-solrcloud-2   default  
                2d8h

PVC:
NAME                                      STATUS   VOLUME                       
              CAPACITY   ACCESS MODES   STORAGECLASS    AGE
data-example-solrcloud-zookeeper-0        Bound    
pvc-a5e996b0-e986-4574-8ad6-50bca74fbb9b   20Gi       RWO            default    
     6h48m
data-example-solrcloud-zookeeper-1        Bound    
pvc-7702b17a-d017-4425-98b0-2c2ed76561bc   20Gi       RWO            default    
     6h47m
data-example-solrcloud-zookeeper-2        Bound    
pvc-87bff553-fdc8-46c6-9d2e-44c6758539e9   20Gi       RWO            default    
     6h46m
example-solr-secret-example-solrcloud-0   Bound    
pvc-6b019f0f-f816-41bf-84ac-51d3c4136ff7   20Gi       RWO            
azurefile-csi   41h
example-solr-secret-example-solrcloud-1   Bound    
pvc-97f51f09-e08e-46a4-86c5-ba52263dbea2   20Gi       RWO            
azurefile-csi   41h
example-solr-secret-example-solrcloud-2   Bound    
pvc-fe1db5e9-dd09-4c97-8383-c2247a094a74   20Gi       RWO            default    
     2d8h


We tried various options to move this azure file but it's not working. We 
didn't find any proper doc for enabling it. Please see the helm configuration 
we currently use.

helm:
      parameters:
        - name: image.tag
          value: "8.11"
        - name: dataStorage.type
          value: "persistent"
        - name: dataStorage.persistent.pvc.storageClassName
          value: azurefile-csi
        - name: solrOptions.security.probesRequireAuth
          value: "false"
        - name: dataStorage.persistent.pvc.name 
<http://datastorage.persistent.pvc.name/>
          value: "example-solr-secret"
      values: |
        solrOptions:
          javaMemory: "-Xms300m -Xmx300m"
          additionalLibs:
          - "/var/solr/data/customjars/"
          security:
            authenticationType: Basic
        podOptions:
          resources:
            limits:
              memory: 2048Mi
              cpu: 1000m
            requests:
              cpu: 50m
              memory: 256Mi
         dataStorage:
           persistent:
             enabled: true
             pvc:
               name: "example-solr-secret"
               accessModes:
                 - ReadWriteMany
               storageClassName: "azurefile-csi"
               azureFile:
                 secretName: example-solr-secret
                 shareName: "apache-solr"
                 readOnly: false


Can you please let me know how we can do this?

Thanks & Regards
Geo P.C.

Reply via email to