https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972050#M2949 The example PatchTransformer $deploy/sas-bases/examples/sas-compute-server/config/compute-server-add-nfs-mount.yaml shows how to add a volume to podTemplates with the label sas.com/template-intent=sas-launcher, which would include batch and compute servers.<BR />Since you'd be adding a PVC instead of an NFS volume, instead of:<BR /> nfs:<BR /> path: {{ PATH-TO-BE-MOUNTED }}<BR /> server: {{ HOST }}<BR />you would use:<BR />persistentVolumeClaim:<BR /> claimName: {{ PVC-NAME }}<BR /><BR />Your LDAP and oauth configurations are persisted in the SAS Configuration Server, so these would not be lost when pods are restarted or you apply new assets. Mon, 04 Aug 2025 13:29:12 GMT gwootton 2025-08-04T13:29:12Z https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/971993#M2948 <P>As the title says, I'd like to add PVCs already created on EKS to SAS Viya 4 compute and batch pods. Documentation doesn't mention about adding PVCs for FSX filesystems. How do I do that?</P><P>&nbsp;</P><P>After making the mounts available in pods, I believe I'd have to run kustomize followed by running kubectl apply commands to apply manifests in site.yaml. When I'd do that, the pods will get recreated and all the LDAP/oauth configuration will be lost. How do I persist these settings between pod restarts?</P> Sat, 02 Aug 2025 04:36:01 GMT https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/971993#M2948 Kamsher 2025-08-02T04:36:01Z https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972050#M2949 The example PatchTransformer $deploy/sas-bases/examples/sas-compute-server/config/compute-server-add-nfs-mount.yaml shows how to add a volume to podTemplates with the label sas.com/template-intent=sas-launcher, which would include batch and compute servers.<BR />Since you'd be adding a PVC instead of an NFS volume, instead of:<BR /> nfs:<BR /> path: {{ PATH-TO-BE-MOUNTED }}<BR /> server: {{ HOST }}<BR />you would use:<BR />persistentVolumeClaim:<BR /> claimName: {{ PVC-NAME }}<BR /><BR />Your LDAP and oauth configurations are persisted in the SAS Configuration Server, so these would not be lost when pods are restarted or you apply new assets. Mon, 04 Aug 2025 13:29:12 GMT https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972050#M2949 gwootton 2025-08-04T13:29:12Z https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972119#M2950 Thanks for the response. Regarding the last part about LDAP/ OAuth, I am concerned that these settings will be lost if I make patch updates and run kubectl apply commands to apply the updates. Isn't that right? Tue, 05 Aug 2025 14:10:07 GMT https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972119#M2950 Kamsher 2025-08-05T14:10:07Z https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972123#M2952 No, that isn't correct. Applying patch updates, version upgrades, or changes to your configuration by rebuilding a reapplying your assets would not remove your existing configurations. Those are persisted in the sas-viya-consul-data-volume-* PVCs. Tue, 05 Aug 2025 15:36:53 GMT https://communities.sas.com/t5/SAS-Viya/Adding-PVCs-to-compute-batch-pods-and-persisting-oauth-LDAP/m-p/972123#M2952 gwootton 2025-08-05T15:36:53Z