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 😭

Microk8s dashboard on remote laptop #networking #raspberrypi #microk8s

https://askubuntu.com/q/1562933/612

“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

'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 💵

On #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. 😅

@arch consider #microk8s & #ansible?

Cc: @geerlingguy

spent the afternoon recovering my #microk8s setup after finding out that the #Acronis backup agent on my hosted vm had no log rotation configured and log-spammed my disk.

Why should I mirror my github repos on a 5 node pi microk8s cluster running gitea? Because I can! 😀 #microk8s #raspberrypi #gitea

When your home-lab setup is older than the greenfield project you are working on and yet more up to date with hardly any tech-debt... okay, comparing apples to oranges, but still, practice what you preach. #homelab #raspberrypi #argocd #microk8s #nix #devops

Playing the first time with #microk8s for some CI tests. Honestly, opposed to other solutions it doesn't feel so micro... #kubernetes #k8s

Accidentally downgraded my home #microk8s cluster to some version from 2022 instead of upgrading it. The following hour was... interesting 😅

A Comparative Analysis of K3s, MicroK8s, and Alternatives

https://htdocs.dev/posts/kubernetes-deployment-strategies-for-small-businesses-on-hetzner-cloud-a-comparative-analysis-of-k3s-microk8s-and-alternatives/

#HackerNews #K3s #MicroK8s #Kubernetes #Alternatives #CloudDeployment

💻 Aufgrund der #Sicherheitslücke(https://www.golem.de/news/auch-in-deutschland-tausende-kubernetes-cluster-lassen-sich-aus-der-ferne-kapern-2503-194691.html) im #nginx von #kubernetes...

gerade mal mein #MicroK8s-#Cluster mit Hilfe dieser Anleitung(https://github.com/canonical/microk8s/issues/4964#issuecomment-2752344329) upgedated

#selfhosting #K8sathome #homelab #k8s #BareMetal

#microk8s cluster rebuilt with #talos and #raspberrypi nodes swapped out for used hp elitedesk minis with i5s and 16GB…

I always forget how much work moving things around in the rack is but the #homelab is chugging away again happily now.

#kubernetes

Автоматизация деплоя: из Bitbucket через Jenkins в MicroK8s — опыт финтех-разработчика

Всем привет! Я — Java-разработчик с пятилетним опытом в финтехе, и сегодня я расскажу, как настроить CI/CD для деплоя Spring Boot приложения из Bitbucket через Jenkins в MicroK8s. Это не просто теория — я поделюсь реальным кейсом, разберу ошибки, с которыми столкнулся, и дам рабочий код. Если вы хотите автоматизировать деплой и не наступать на грабли — поехали! Представьте: у вас есть микросервис на Spring Boot, который нужно быстро и без ошибок доставить в продакшен. Ручной деплой отнимает время, а команда требует стабильности. Я решил эту задачу с помощью Bitbucket, Jenkins и MicroK8s, но путь оказался не таким гладким, как хотелось бы. Проблемы с аутентификацией, конфликты портов и настройка окружения заставили меня попотеть. Как я справился? Об этом — в статье. CI/CD (Continuous Integration/Continuous Deployment) — это must-have для современных разработчиков. Автоматизация сборки, тестирования и деплоя приложений экономит время, снижает вероятность ошибок и ускоряет доставку кода до продакшена. В этой статье мы разберем, как настроить полноценный CI/CD-пайплайн для Spring Boot приложения, используя связку Bitbucket, Jenkins и MicroK8s.

https://habr.com/ru/articles/891844/

#ci_cd #bitbucket #jenkins #microk8s #spring_boot #kubernetes #делой #автоматизация #devops #pipline

#Talos #kubernetes single node cluster up and running with #Calico, #MetalLB, #Traefik and a test #whoami deployment

In no way scientific but it feels much more responsive that #microk8s

Next step to rebuild a clean node and then migrate some services

Сканируем кластер Kubernetes без лишних сущностей

Обеспечение безопасности инфраструктуры является неотъемлемой частью процессов DevSecOps. На сегодняшний день для работы различных приложений используются контейнеры, а для управления ими применяется Kubernetes. Когда речь заходит о безопасности контейнеров, то обычно все вспоминают о сканировании образов и поиске в них уязвимостей. Но при этом не стоит забывать и о безопасности самой среды оркестрации Kubernetes, которая управляет всеми нашими контейнерами. О безопасной настройке Kubernetes написано немало статей, однако важно понимать, что недостаточно один раз безопасно настроить. Необходимо периодически проверять уровень защищенности K8s, а в этом лучше всего помогут сканеры безопасности, некоторые из которых мы сегодня и рассмотрим.

https://habr.com/ru/companies/otus/articles/879422/

#kubernetes #minikube #microk8s #security #k8s

hey folks who know their postgres and kubernetes, can you help me with this mystery?

i have a bare-metal kubes setup and I'm benchmarking options for cloudnative-pg storage, namely those two

1. longhorn (replica bound) clocks at about 3000 tps
2. microk8s-hostpath storage scored only about 480 tps

that's 6 times slower. why is that? i thought hostpath would provision local PV and it should be faster than longhorn

#kubernetes #postgresql #microk8s

OK, so I've found fixes for both the problems I ran into yesterday trying to run microk8s on Fedora 41.

I've updated the blog post with the details

https://blog.hardill.me.uk/2024/12/06/microk8s-on-fedora-41/

#Fedora #microk8s #k8s #snap

Microk8s on Fedora 41

https://blog.hardill.me.uk/2024/12/06/microk8s-on-fedora-41/

Having wasted a half a day trying to setup what was meant to a really quick test environment for a specific feature, here are the notes I made along the way to get a working system

I have a multi node microk8s cluster that I run a bunch of things (personal FlowFuse instance, InfluxDB, Grafana, Keycloak…) but I needed a separate Kubernetes cluster to run a test on.

I already had a Fedora […]

#Fedora #microk8s #snap