prometheus
Upgrade to Prometheus v2.50.1
No issues with this by means of Docker-compose YAML automated GitOps minor update of the Docker container and on the K3s Kubernetes cluster by means of Flux. 2.50.0 / 2024-02-22 2.50.1 / 2024-02-26
docker
GitLab
Upgrade GitLab Runner to chart version 0.62.1 and app version 16.9.1
No problems deploying GitLab Runner to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. And also by means of Watchtower infrastructure to Docker host for Image Lifecycle Management. Helm Chart 0.62.1 v16.9.1 (2024-02-28)
ghost
Upgrade to Ghost 5.80.0
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.80.0
rocket.chat
Upgrade to Rocket.Chat 6.6.2
No problems automatically updating the Docker image and run the container by Watchtower for Bierochs and Tanzcrew teams. 6.6.2
git
Upgrade to GitLab 16.9.1
No problems automatically updating the monolithic Docker image and run the container by Watchtower. GitLab Security Release: 16.9.1, 16.8.3, 16.7.6
enterprise wiki
Upgrade of XWiki 16.1.0
Easy major upgrade of latest stable Docker container to new micro version by Watchtower infrastructure and manual in application upgrade by administration access. Release Notes for XWiki 16.1.0
code
Upgrade to Collabora Online Development Edition 23.05.9.2.1
Successful update of the Docker container by means of Watchtower. CODE 23.05 Release Notes
ghost
Upgrade to Ghost 5.79.6
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.79.5 v5.79.6
metabase
Upgrade of Metabase v0.48.7
No problems upgrading the Docker container with a Docker compose yaml file and by means of Watchtower infrastructure. Metabase v0.48.7
pi-hole
Upgrade to Pi-hole 2024.02.2
On all three nodes I upgraded Pi-hole successfully by means of fully automated Watchtower Docker container update. On the CentOS 7 VM i had to recreate a sym-link to /etc/lighttpd/conf-enabled/99-unconfigured.conf within the container. 2024.02.1 2024.02.2
mastodon
Upgrade to Mastodon v4.2.8
Micro but critical update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow. v4.2.8
pi-hole
Upgrade to Pi-hole 2024.02.0
On all three nodes I upgraded Pi-hole successfully by means of fully automated Watchtower Docker container update. On the CentOS 7 VM i had to recreate a sym-link to /etc/lighttpd/conf-enabled/99-unconfigured.conf within the container. 2024.02.0