#GitOps for #Kubernetes With Nixidy and #ArgoCD
Someone wrote about my project nixidy!
https://tech.aufomm.com/gitops-for-kubernetes-with-nixidy-and-argocd/
#GitOps for #Kubernetes With Nixidy and #ArgoCD
Someone wrote about my project nixidy!
https://tech.aufomm.com/gitops-for-kubernetes-with-nixidy-and-argocd/
Wait, there is a new #nat64 implementation for linux besides jool and the very old tayga?
And it only consists out of some network namespaces and a ebpf tc filter?
Looks quite interesting.
https://github.com/kubernetes-sigs/nat64/blob/main/tests/integration/e2e.bats
New Release! Master Kubernetes from Scratch: The Beginner's Guide to Kubernetes Fundamentals by Kirshi Yin #books #ebooks #newreleases #programming #kubernetes #k8s
Get started with Kubernetes from scratch.
Find it on Leanpub!
New Release! Master Helm Fast: The Easy Guide to Kubernetes Deployment by Kirshi Yin #books #ebooks #programming #k8s #kubernetes #newreleases
Helm is a must-have tool for anyone working with Kubernetes. It simplifies managing complex deployments, automates repetitive tasks, and much more. By mastering Helm, you'll save time, reduce errors, and bring consistency to your deployments—essential skills for any modern IT professional.
Find it on Leanpub!
So I built out this whole thing to manage #k8s pods like a DaemonSet except with predictable templated names and an auto-generate service. Tests work, everything looks like it should work, except... it doesn't.
Turns out I've been foiled by a limitation built into Metacontroller since forever: namespaced metacontrollers can't talk to cluster-scoped objects.
Cool. Cool cool cool. I guess I'll just do this with a cron? Ugh.
Anger-inducing bullcrap of the day: projects that package their Ansible collection in a way, where the only way to use it is, to execute the included playbooks standalone.
Instead of just using multiple roles within the collection - or multiple entrypoints within the role.
You know, just like normal people do.
This breaks every sane architectural convention and composability
Looking at you, #kubespray
So, having a home #k8s cluster something about Posgres HA has been bugging me a lot. When there's an electric blackout (this is #Spain after all), all the pods go down. But what happens with Postgres is that the replicas go into a process to sync and elect a new master, and this takes time.
Meanwhile, the pgpool will give successful database connections to apps in pods, but only read-only.
What happens with an app like #Matrix #Synapse is that I think it gets database connections in a pool at start-up, and as it succeeds, it just continues. However, when it actually tries to make updates and inserts, it will get errors, but now it will only log them; they aren't fatal. Or would log them unless the logs were by default off because of privacy and security.
The initial read-only database connections are never upgraded to read-write because the application doesn't expect this kind of a failure, even when the new master is chosen.
Meanwhile the Matrix server continues in a highly degraded mode without being able to persist messages sent. It will only be able to relay them to currently connected online clients. This leads to users getting diverging views to the messages on channels.
I solved this by adding an initContainer to check for read-write connection to Postgres before the Synapse pod start-up, but it's a hack.
I'm always happy to delete a #k8s cluster.
#til podman lepiej wspiera pliki kubernetes niż pliki docker compose. I super, bo właśnie korzystam z niego do testowania, a środowisko produkcyjne mam na k8s, czyli nie muszę mieć oddzielnego pliku dla compose
#IngressNightmare – czyli jak przejąć klaster Kubernetes
Podatności określane jako krytyczne mogą wzbudzać skrajne emocje. W sekuraku jesteśmy pewni, że nie wszyscy zgodzą się z punktacją CVSS 3.1 (9.8/10) przypisaną do serii podatności określonych jako IngressNightmare, które zostały opisane 24.04.2025 przez badaczy z wiz.io. TLDR: Problematycznym komponentem jest Ingress NGINX Controller, czyli ingress controller (kontroler ruchu wejściowego,...
#WBiegu #Ingress #K8s #Kubernetes #Nginx #Podatność #Rce
https://sekurak.pl/ingressnightmare-czyli-jak-przejac-klaster-kubernetes/
#k8s is supposed to be pronounced "keights" or "kates", not some strange thing like #kubernetes!
〈Cloud周報第221期:紅帽要將邊緣運算主機搬上太空,全球最大期貨交易所啟動雲端分散通用帳本計畫〉
雲端重點新聞(2025/2/20~3/28)
#邊緣運算 #K8s
紅帽和太空旅遊新創聯手,計畫將邊緣運算主機搬上國際太空站
https://www.ithome.com.tw/news/168120
Me 2 years ago: #Kubernetes is software with biggest regeneration ability.
Me 6 months ago: Wow, Longhorn has even better regeneration ability!
Me now: What the hell, Patroni has the best regeneration ability I have ever seen!
Welcome to our brave new world of self-fixing things...
Okay, I've been asked this question to which I was not prepared: where do you go if you want to learn Kubernetes from the ground up? Consider a person who doesn't even know how to run "docker" in their own laptop, but they want to rise to a point where they can actually manage a Kubernetes cluster. Thoughts?
#HomeLab #Kubernetes #SysAdminLife #k8s #SRE
I don't know why, but every time I look at using the postgresql operator, I get nervous about it and never end up deploying it.
Right now my DBs are all on a single "big" postgresql instance.
This is the most cursed idea I have seen published in a long time
Et si l'on vous disait que le #GitOps, ce n'est pas que mettre dans #Git ce que vous déployez, mais aussi une philosophie et des concepts!
J'aurai l'honneur de vous en parler à @devoxxfr 2025!
Et pour m'accompagner, le plus mignons de tous les robots ! #astro
https://link.davinkevin.fr/AstroGitOps-devoxxfr25-program
Si vous avez des questions et/ou des retours d'expériences, n'hésitez pas à me pinger !
Et n'oubliez pas de mettre la prez dans vos fav ️