Operational memory now survives pod restarts and helm uninstall
Chart parity with deploy/dashboard.yaml plus hardening from in-cluster
verification on multi-node minikube:
- Persistence: templated PVC (persistence.enabled/size/storageClassName/
existingClaim), annotated helm.sh/resource-policy: keep so operational
memory survives helm uninstall; strategy Recreate when enabled (RWO) - Namespace: remove templated namespace (use --create-namespace);
namespace helper resolves .Release.Namespace so -n is honored - Volume ownership: fsGroup 65534; values-toggled volumePermissions
init container for provisioners that ignore fsGroup on hostPath
(minikube default) — symptom was silent NullStore fallback - nodeSelector support — required on multi-node minikube where hostPath
PVs have no node affinity (rescheduled pod mounts empty dir) - NOTES.txt, chart README (persistence, minikube gotchas, local image
workflow, full values table), root README refreshed (timeline, blast
radius, operational memory; chart declared canonical) - Chart 0.1.0 → 0.2.0, appVersion → v1.7.0; dashboard.yaml image bumped