flux
Upgrade to Flux 0.40.0
Updated successfully via Homebrew and CLI bootstrapping Proxmox VE K3s Kubernetes cluster. v0.40.0
flux
Updated successfully via Homebrew and CLI bootstrapping Proxmox VE K3s Kubernetes cluster. v0.40.0
ghost
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.35.1
portainer
No problems deploying to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. Also the corresponding agents were automatically rolled out via Watchtower infrastructure on the Docker-only nodes including arm node. Release 2.17.1 Helm Chart 1.0.40
homer
No problems automatically updating the Docker image and run the container by Watchtower for website Bierochs. v23.02.2
GitLab
No problems deploying to K3s cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. Helm Chart 0.49.3 v15.8.3 (2023-02-19)
mariadb
Successfully upgraded the Docker container on the Database Host by means of Portainer and K3s Kubernetes Cluster Flux V2 GitOps automation and manually upgraded databases. MariaDB 10.11.0 Release Notes MariaDB 10.11.1 Release Notes MariaDB 10.11.2 Release Notes
So very easy upgrade, done within no time and no problems whatsoever with this dockerized mailcow instance. 🐥🐄 Febmooary Update 2023 - Update II (a) - ClamAV, Netfilter & UI Improvements
hedgedoc
No problems upgrading the Docker container with a Docker compse yaml file within Portainer and by means of Watchtower DevOps. HedgeDoc 1.9.7
kube-prometheus-stack
No problems deploying Prometheus Helm chart to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. Helm Chart 45.2.0
ghost
On both domains I upgraded Ghost successfully by means of Watchtower Docker container update. v5.34.0 v5.34.1 v5.35.0
kube-prometheus-stack
No problems deploying Prometheus Helm chart to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach. Application v0.63.0 Helm Chart 45.1.1
istio
No issues whatsoever by manually upgrading by means of istioctl and redeploying affected workloads resp. pods in the K3s Kubernetes cluster. Istio 1.17.0 Announcing Istio 1.17 Istio 1.17.0 Change Notes