Graph Studio Deployment with NFS Storage

Overview and Use Case

This configuration is used to deploy Graph Studio with an external Network File System (NFS) storage volume. It is designed for environments where Graph Studio needs access to external shared storage for dataset imports/exports and cross-component staging with Graph Lakehouse. For shared staging architecture and access requirements, see Shared storage architecture.

Custom Resource Definition

apiVersion: anzo.cambridgesemantics.com/v2
kind: Anzo
metadata:
  name: server
  annotations:
    cambridgesemantics.com/skip-lb-check: "false"
spec:
  nodeConfig:
    spec:
      replicas: 1
      serviceName: anzo-server
      selector:
        matchLabels:
          app: "anzo"
      template:
        metadata:
          labels:
            app: "anzo"
        spec:
          serviceAccountName: anzo-operator
          containers:
          - name: anzo
            image: artifacts.altair.com/graph-docker/anzo:6.3.1
  role: AnzoServer
  jsonActivation: true
  initJSON: |-
    {
      "sysadminUser": "k8s://anzo-server/admin_user",
      "password": "k8s://anzo-server/admin_password",
      "hostname": "server",
      "serverId": "${SERVER_ID}",
      "licenseEncoded": "${CSI_LICENSE}"
    }
  volumes:
  - name: nfs1
    mountPath: "/opt/nfs1"
    pv:
      capacity:
        storage: 5Gi
      accessModes:
      - ReadWriteMany
      storageClassName: ""
      persistentVolumeReclaimPolicy: Retain
      nfs:
        path: "${NFS_EXPORT_PATH}"
        server: "${NFS_SERVER}"
        readOnly: false
    pvc:
      accessModes:
      - ReadWriteMany
      storageClassName: ""
      resources:
        requests:
          storage: 2Gi