Adding PVCs to compute, batch pods and persisting oauth/LDAP config after applying msnifests

[Kamsher]

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?

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?

[gwootton]

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.
Since you'd be adding a PVC instead of an NFS volume, instead of:
nfs:
path: {{ PATH-TO-BE-MOUNTED }}
server: {{ HOST }}
you would use:
persistentVolumeClaim:
claimName: {{ PVC-NAME }}

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.

[Kamsher]

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?

[gwootton]

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.