What is your update policy? Are you on auto update, or do you manually go over stuff, do you pick a day to just flush it all though, or are you just on an old version?
Share why and how you run your updates? I would like to hear how you all manage them
Version are pinned in code. Helm chart, image, RKE2 and OS. Let fleet/argocd/helm handle most upgrades. Infrastructure/management upgrade (Rancher app or rancher cluster components, Forjeo, Harvester, keycloak, etc) get a dedicated virtual testing cluster spun up and manual and automated tested (I don’t have good virtual networking testing yet once I do KubeOVN only that might be truly possible). Renovate runs to automatically update all the version numbers.
Checks every 15 min for apps, every hour for infra.
Id love to try to get a web hook from my security scanner to push for an update sooner if a VEX item is identified, but shrug
Mind you, I like running my homelabs, the idea it serves anything useful is just to prove I can lol. They go down all the time too because I’m monkying with the hardware config ALL the time.
@JelleWho I’m running Home Assistant as container with podman quadlet.
I’m using an Ansible Playbook, which is executed manually for updating of Home Assistant.If a new HA container image has been fetched, the podman quadlet is stopped, a backup of the container volumes is executed and afterwards the podman quadlet is started again, using the new container image for the container.
Didn’t know there was an auto update?! I run them on a random schedule when I’m bored. While commuting with the bus and no one is home. Or while watching YouTube videos in the evening.
Update policy?
I see update, I click update!
ROLL DICE BABY!
it does backups… somewhere… I think…
