Upgrade Procedures
Keeping platform components up to date is important for security and feature access. This page covers the upgrade process for each layer of the stack.
What this page covers
- Docker image upgrades: pull and recreate
- Helm chart upgrades:
helm upgrade - K3s version upgrades
- Database migration considerations
- Upgrade order and dependencies
Docker image upgrades (Docker-only track)
For Docker Compose services, update the image tag in docker-compose.yml or pull the latest tag:
docker compose pull
docker compose up -d
Always read the release notes before upgrading to a new major version — YouTrack and Gitea occasionally require migration steps.
Helm chart upgrades (K3s track)
helm repo update
helm upgrade <release-name> <chart> --namespace <namespace> -f values.yaml
For the kube-prometheus-stack, check the chart's upgrade notes — CRD updates sometimes require manual steps.
K3s version upgrades
K3s supports in-place upgrades via the k3s upgrade script or the system-upgrade-controller Kubernetes operator.
# Manual single-node upgrade
curl -sfL https://get.k3s.io | sh -
For multi-node clusters, upgrade the server node first, then agent nodes one at a time.