#microk8s — Public Fediverse posts

Well, now that I'm home for a bit, I thought I'd get rid of nginx-ingress from my #homelab because the drama of its deprecation finally got to me.

I have chosen the path of least resistance (by using #microk8s, no less). You can chastise me, I understand the reasons why you do, but like someone has said elsewhere, Marcus Aurelieus has already given me permission to not care.

it was actually very easy to do it in the 1.35.0 release; just an addon disable, and subsequent enable.

So here we are, nothing much has changed, the world didn't end in the last 60 days because I failed to upgrade, and my homelab still isn't exposed to the outside world.

Hum ?

#orchestration #k8s #k3s #microk8s

Hum ?

#orchestration #k8s #k3s #microk8s

Hum ?

#orchestration #k8s #k3s #microk8s

Hum ?

#orchestration #k8s #k3s #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 😭

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 😭

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 😭

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 😭

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”, 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”, 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”, 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”, 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 💵

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

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

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

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

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

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

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

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

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.

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.

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.

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.

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.

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

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

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

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

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

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

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

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

#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

#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

#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

#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

Автоматизация деплоя: из 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

Автоматизация деплоя: из 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

Автоматизация деплоя: из 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