Storage
Plan shared media and app configuration storage.
Apps may use shared NFS storage for media and separate persistent volumes for application configuration. The exact layout is chart-specific. A shared volume is accessible to every workload that mounts it, even across namespaces; a separate config claim does not isolate shared media. Review each chart’s storage notes and plan backups. Some databases require local or block storage rather than shared NFS.
How it works
Charts declare persistent volume claims and mount points; Kubernetes binds claims to storage supplied by the cluster. Multiple apps can mount a shared NFS export for common media, while app-specific configuration may use its own claim when the chart supports it. Access follows the mounts and permissions configured for those workloads—not just their namespace—so review each chart’s paths and backup requirements.
These views show or configure aspects of your Kubernetes cluster. Availability and behavior depend on your deployed components, cluster configuration and supported app charts.
Check the result: Use Kubernetes workload status and the relevant chart documentation to verify behavior. Observability views show reported state and do not themselves enforce network or storage boundaries.