Ben HardillAnother joy of slowly upgrading this microk8s cluster, trying to update the bundled version of Metallb only to discover that they have pulled all their container images from Docker Hub (luckily they are all on quay.io so I can just edit the image tags)
Wet, windy Saturday, perfect day to try and upgrade my microk8s cluster, but it appears that I can't get my new Ubuntu 26.04 node to join my old 1.24 cluster at 1.25 because it can't find the yaml python module.
I thought the point of a snap was that all the dependencies were bundled in?
dada
Nic Roland 
My god... I've been having #microk8s cluster issues all week and I finally figured out that it's because of a failed auto-refresh of the core22 #snap
I've tried various approaches; clearing cache, removing downloaded snaps manually and I've been walking through the refresh again and nope - still fails to 'copy snap data'...
I know that disk space isn't an issue during the upgrade and the logs are terse so I'm really convinced I've no other path forward and that a rollback is warranted... BUT... Snapd won't allow me to revert the package because it's not currently active (because the upgrade failed)... Hurray! When an unattended upgrade fails, you're not allow to roll back!! Is that considered a desirable feature in a package manager?
If I can't find a safe way to restore this base-snap, I'll be forced to pursue more drastic measures which could result in loss of #k8s state and I'll need to rebuild my cluster... and I've literally been trying to work on disaster recovery for cluster when this all happened 😭
रञ्जित (Ranjit Mathew)“AWS To Bare Metal Two Years Later: Answering Your Toughest Questions About Leaving AWS”, OneUptime (https://oneuptime.com/blog/post/2025-10-29-aws-to-bare-metal-two-years-later/view).
Via HN: https://news.ycombinator.com/item?id=45745281
On Lobsters: https://lobste.rs/s/ku4lrn/aws_bare_metal_two_years_later_answering
#AWS #Cloud #BareMetal #DIY #Savings #Kubernetes #MicroK8s #K8s
Mœllus'AWS to Bare Metal Two Years Later: Answering Your Toughest Questions About Leaving AWS' https://oneuptime.com/blog/post/2025-10-29-aws-to-bare-metal-two-years-later/view /via #oneuptime #microk8s #talos #aws #k8s 💵
Alejandro BaezOn #k8s, the complexity is on knative rollout. But if you strip down to nothing, it becomes easier. knative serving CRDs with #kourier, and you get something that work for requests cross nodes easy. pro and con are, you now have a whole bloody k8s cluster. 🤣 Heavy at start, but light in maintaining after. Especially if this is a #talos or single node #microk8s/#k3s setup. 😅
Wintermute_BBS
Christian K 🍉Why should I mirror my github repos on a 5 node pi microk8s cluster running gitea? Because I can! 😀 #microk8s #raspberrypi #gitea