Open shazada opened 1 year ago
Hi @shazada , The approach is to import your existing NFS export as a kubernetes volume within the appropriate storageClass and create a pvc for it in the right namespace before deploying. Once done, you should be able to point the deployment to the volume using:
repository:
persistence:
enabled: true
existingClaim: myNFSexport
More (hopefully useful) details can be found here: https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/storage.md
@alxgomz thanks! I'll try that.
And how does this work with the service account then: https://github.com/Alfresco/acs-deployment/commit/f03a7a59496de85b585d07160a47fd4ad01bcfa2#diff-becdf0661f6bb1923c084bf71ae8ae8dd78285bd61c4046e839c9f91ca65c44fL192
If I add the NFS without suppliying this serviceAccount whith has NFS capabilities the POD can't connect to NFS.
Which CSI driver are you using? Usually we use the EFS CSI drivers which do not requires anything specific (though we use it with dynamic provisioning)
Oh I took a second look and I think you might be using the in-old tree kubernetes storage driver (which options such as server
and path
).
I remember testing it but that was loooong ago back in the 1.0.x version of the chart. Back then I don't remember any requirement for a service account but of course things may have changed with kubernetes upgrades. Though I dind't find any reference of that in the kubernetes examples.
Having said that. We do not support direct PV usage in deployments and instead require to have a PVC on top of it.
If using this approach you still see the need for. a serviceAccount please let us know what exact API persmission that account needs so we can understand if/where we miss something.
So the use-case is:
So i'm not sure if what we're doing is wrong --> but it's how we've done it in the past years. At this point when you deploy REPO it triggers the following helper: https://github.com/Alfresco/alfresco-helm-charts/blob/main/charts/alfresco-common/templates/_helpers-persistence.tpl#L5 This creates a
- name: data
If we disable persistance it still creates the data volume with emptydir 20GI. Our override_values.yaml looks like this
So it fails to create another data volume, because the previous created bij the helper-class already exist. To counter this, I've to change the default chart and put and if else around this include: https://github.com/Alfresco/acs-deployment/commit/f03a7a59496de85b585d07160a47fd4ad01bcfa2#diff-becdf0661f6bb1923c084bf71ae8ae8dd78285bd61c4046e839c9f91ca65c44fL194