Add NFS support: implement setup scripts, Kubernetes integration, and configuration files

infrastructure_setup/README.md

@@ -23,7 +23,10 @@ Internet → External DNS → MetalLB LoadBalancer → Traefik → Kubernetes Se
 - **Traefik** - Handles ingress traffic, TLS termination, and routing
 - **cert-manager** - Manages TLS certificates
 - **CoreDNS** - Provides DNS resolution for services
+- **Longhorn** - Distributed storage system for persistent volumes
+- **NFS** - Network file system for shared media storage (optional)
 - **Kubernetes Dashboard** - Web UI for cluster management (accessible via https://dashboard.internal.${DOMAIN})
+- **Docker Registry** - Private container registry for custom images
 
 ## Configuration Approach
 
@@ -44,3 +47,55 @@ All setup scripts are designed to be idempotent:
 - Changes to configuration will be properly applied on subsequent runs
 
 This idempotent approach ensures consistent, reliable infrastructure setup and allows for incremental changes without requiring a complete teardown and rebuild.
+
+## NFS Setup (Optional)
+
+The infrastructure supports optional NFS (Network File System) for shared media storage across the cluster:
+
+### Host Setup
+
+First, set up the NFS server on your chosen host:
+
+```bash
+# Set required environment variables
+export NFS_HOST=box-01                    # Hostname or IP of NFS server
+export NFS_MEDIA_PATH=/data/media         # Path to media directory
+export NFS_STORAGE_CAPACITY=1Ti          # Optional: PV size (default: 250Gi)
+
+# Run host setup script on the NFS server
+./infrastructure_setup/setup-nfs-host.sh
+```
+
+### Cluster Integration
+
+Then integrate NFS with your Kubernetes cluster:
+
+```bash
+# Run cluster setup (part of setup-all.sh or standalone)
+./infrastructure_setup/setup-nfs.sh
+```
+
+### Features
+
+- **Automatic IP detection** - Uses network IP even when hostname resolves to localhost
+- **Cluster-wide access** - Any pod can mount the NFS share regardless of node placement
+- **Configurable capacity** - Set PersistentVolume size via `NFS_STORAGE_CAPACITY`
+- **ReadWriteMany** - Multiple pods can simultaneously access the same storage
+
+### Usage
+
+Applications can use NFS storage by setting `storageClassName: nfs` in their PVCs:
+
+```yaml
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: media-pvc
+spec:
+  accessModes:
+    - ReadWriteMany
+  storageClassName: nfs
+  resources:
+    requests:
+      storage: 100Gi
+```