I\u2019m starting to work on deploying Nextcloud on Kubernetes, which should eventually replace my existing setup. I\u2019ve been running Nextcloud using the official Snap package for years, and overall it has worked well. The main issue, however, is performance – it\u2019s been quite slow at times. On top of that, I\u2019m paying for a dedicated VM just to run it, which doesn\u2019t feel very efficient anymore.<\/p>\n\n\n\n
So, it\u2019s time to move it into my Kubernetes cluster.<\/p>\n\n\n\n
In Part 1, I\u2019ll focus on setting up the core components – the database, NGINX, and the basic pieces needed just to get the service up and running. Later on, I\u2019ll start adding the more advanced stuff: Redis, scaling with multiple pods, and some extra security improvements.<\/p>\n\n\n\n
I might also experiment with a Helm-based<\/a> approach at some point, but for now, I want to build everything from scratch to better understand how it all fits together.<\/p>\n\n\n\n\n\n\n\n docker hub official<\/strong>: https:\/\/hub.docker.com\/_\/nextcloud<\/a> My first attempt with installation is to basically convert the official docker compose<\/a> file to Kubernetes. Redis later:). I will use sidecar container for reverse proxy + FPM.
My choice of image<\/strong>: 33-fpm. 33-fpm will always use version 33, This automatically tracks the latest 33.x release (e.g. 33.0.1, 33.0.2, etc.), so I don\u2019t have to manually bump patch versions.
nginx:lates<\/strong> because FPM need reverse proxy
mariadb:11.8<\/strong> – will be my database<\/p>\n\n\n\n
<\/p>\n\n\n\n