#microk8s — Public Fediverse posts

RE: https://mastodon.social/@hynek/116917170834518173

Currently running docker swarm in a small team and hit enough rough edges that need to move container orchestration to something else (swarm also not really actively maintained) - nomad was on the list but fortunately avoided switching before hashi stuff went bad (below experiences help feel this was the right call)

Thinking of making the jump to #microk8s or one of the other lightweight #k8s distros - any recommendations or war stories?

Another 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)

#k8s #kubernetes #microk8s

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?

#k8s #kubernetes #microk8s

Hum ?

#orchestration #k8s #k3s #microk8s

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 😭

“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. 😅

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

#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

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

OK, that was a fight

microk8s on fedora 41 needs the following

- totally disable SELinux
- turn off firewalld (or ingress doesn't work)

#k8s #fedora41 #microk8s #kubernetes

Been continuing my adventures of building an #ansible role for #microk8s which worked well and got me to a working thing with a giant but involved.

Apparently one can not properly run molecule test scenarios involving snap packages when using containers for testing.

I found https://bugs.launchpad.net/snapd/+bug/1712808 and wonder if testing in containers might simply be impossible.

PPS it does looks like disabling the #microk8s rook-ceph addon would destroy the rook-ceph namespace even though the addon was not installed with microk8s 😱

#homelab

Interesting… it looks like #microk8s addins will show as enabled even if they weren’t installed using microk8s enable… so now I will need to remember which truly are an addon and which are not. Hopefully have this in my install notes! 🤞

PS not sure how much this matters other than the microk8 list being accurate. Luckily it won’t try to upgrade addons as part of a kubernetes upgrade… I was just curious why rook-ceph (and others) showed up as enabled…

#homelab

Wrote an #ansible script to upgrade the #microk8s cluster from 1.29 to 1.30. Seems like it might have worked... 🤞

Taking a backup now then will let the cluster settle down for a while before going to 1.31

#homelab

@Coreyja I've built clusters with #Ubuntu and #microk8s, and have colleagues who speak highly of #k3s.

If you build a heterogeneous cluster with Arm and x64 nodes, be aware that few helm charts are built to handle that case. A homogeneous cluster is far simpler in that regard.

#Canonical Observability Stack(COS)을 이용한 모니터링 시스템 구축을 소개합니다! #조동원 #김세영 님의 워크샵에서는 #Juju와 #microk8s, #COSLite를 활용하여 모니터링 시스템을 구축하는 방법을 다룹니다. Juju의 개요와 함께 Juju 소개, 부트스트랩, 그리고 다양한 기능을 살펴보고, microk8s의 개요와 배포 방법을 설명합니다. 마지막으로 COS Lite를 배포하고, 다른 컴포넌트를 모니터링하는 방법과 구성 요소를 파헤쳐 봅니다. #모니터링 #시스템구축 #CanonicalObservabilityStack #오픈소스 #클라우드 #UbuCon Korea

키사이닝 파티도 많은 참여 부탁드립니다!
https://discourse.ubuntu-kr.org/t/ubucon-korea-2024-openpgp/49569

From this week's ADMIN Update: Andreas Stolzenberger looks at three simple, compact Kubernetes distributions for operation on edge devices or in small branch office environments. https://www.admin-magazine.com/Archive/2024/80/Simple-small-scale-Kubernetes-distributions-for-the-edge
#Kubernetes #cluster #K3s #MicroShift #RHDE #MicroK8S

Canonical Launches Data Science Stack for Data Science and Machine Learning Beginners #DataScienceStack #DSS #Datascience #MachineLearning #Ubuntu #Pytorch #Tensorflow #Microk8s #Jupyterlab #MLflow #Linux
https://ostechnix.com/canonical-data-science-stack-dss/

Looking to extend my raspberry pi kubernetes cluster into storage…

Does anyone have #homelab performance results for a raspberry pi ceph cluster? Considering making the leap! Will three pi5 nodes be sufficient for managers monitors and osds for a basic HA cluster or do I need more?

#ceph
#raspberrypi
#kubernetes
#microk8s
#rook

Been using #microk8s addons (Ingress, Cert-Manager, Observability, NFS) for a while now in my #homelab. Been a great way to quickly get the infra I need up and running so I can focus on deploying the fun services (Jellyfin, syncthing, etc.)

What other addons have people found useful?

#kubernetes #k8s

@forquare our deployments were significantly replayable against #eks as well as #microk8s varying only in select overlays, which was quite nice. That and being a #canonical / #ubuntu fanboi doesn't hurt :)