nextcloud

A team may want shared files and collaboration tools while choosing where its data is stored and operated. Nextcloud provides that server application, allowing people to access and share files through a central service. Its Kubernetes chart is a deployment mechanism rather than the application itself. Reliable operation depends on preserving files, user records, configuration and installed apps together, with access and upload behavior matched to the way users reach the site.

Current guidance

The original record links to the application project. The Nextcloud Helm repository describes its chart as maintained by community volunteers for expert use and explicitly says it is not supported by Nextcloud GmbH. Chart, server and container-image support must therefore be checked separately.

A Kubernetes deployment needs a coherent plan for application data, configuration and the database. Match database and PHP requirements to the selected Nextcloud server release, configure background jobs, and review Redis-backed file locking where appropriate. The administration manual covers these application concerns independently of chart values. Reverse-proxy headers, trusted domains, upload limits and TLS behavior must also match the ingress path users actually take.

Back up and test restoring data, configuration, the database, custom apps when installed, and themes together. Follow the documented maintenance-mode procedure to avoid inconsistent backups; a persistent-volume snapshot alone may omit required state. Exercise large uploads, background processing and a controlled upgrade with compatible apps enabled. Scaling the web pods adds requirements for shared storage and coordinated application state; it does not by itself create high availability. Record the chart, server image and bundled app versions separately. This review supplies operating context but has not validated a particular storage backend or multi-replica deployment.