Gesucht: Linux Systemadministrator (m/w/d) – Cloud-Infrastruktur
Wo: Geisenhausen bei Landshut, Niederbayern (hybrid)
https://www.adito.de/karriere/linux-systemadministrator.html

Gesucht: Linux Systemadministrator (m/w/d) – Cloud-Infrastruktur
Wo: Geisenhausen bei Landshut, Niederbayern (hybrid)
https://www.adito.de/karriere/linux-systemadministrator.html
Ok, time to deploy Anubis in front of Gitea, I'm done with those FAANG oligarchs scraping my repos 24/7 to check if anything changed...
F*ck off.
But that also means Gitea might get unstable for some time, woops
If you are curious : https://git.halis.io
If you see the cute furry, it worked
«This is precisely why Kubernetes is so notoriously difficult to work with. It’s not difficult because distributed systems are inherently complex (though they are). It’s difficult because Kubernetes is fundamentally an assembler of garbage.»
https://andreafortuna.org/2025/06/20/unpopular-opinion-kubernetes-is-a-symptom-not-a-solution
/via @jbz
iX-Workshop: Fortgeschrittene Administration von Kubernetes
Lernen Sie fortgeschrittene Techniken für das Applikationsmanagement und die Implementierung von Service-Mesh-Technologien.
Things get interesting, the replacement of kube-proxy and the nginx ingress by things in Cilium made #kubernetes a lot easier. Not entirely sure about the new Gateway API but one shall see
I'm building a #Bluesky custom feed that filters the firehouse using #MachineLearning on my #Linux #Ubuntu home server underneath a Minikube #kubernetes VM.
I'm in awe on how many stages (three!) I need to deploy to consume the posts, and allow access to the filtered results.
First, a reverse proxy at the internet border. Then a minikube tunnel to allow access into the VM. Then an ingress controller to manage the traffic flows within the VM itself.
Mind boggling complexity!
Puzzle ITC ist heute mit Vorträgen und als Sponsor bei der #tuebix vertreten. Thematisch geht es um #Kubernetes Container Security und #Ansible Tricks und Kniffe
Docker Desktop 4.43 expands AI support with better model controls, OAuth-secured MCP tools, and instant Compose-to-Kubernetes conversion.
https://linuxiac.com/docker-desktop-4-43-debuts-powerful-compose-bridge/
I've been disappointed about this for at least the last decade, but if you feel that the polling-based designs of Kubernetes and Prometheus are "wrong", here's some science:
https://arxiv.org/abs/2507.02158
Kubernetes is a symptom, not a solution
https://andreafortuna.org/2025/06/20/unpopular-opinion-kubernetes-is-a-symptom-not-a-solution
And why did I choose Talos Linux instead of k3s, minikube, or so many other ways to deploy Kubernetes? Very simple answer: immutable deployment + GitOps. I have a number of hosts that need to run apt/dnf update on a regular basis. As much as this can be automated, it is still tiresome to manage. I don't have to worry as much about an immutable host running a Kubernetes cluster, mostly because the bulk of the attack surface is in the pods, which can be easily upgraded by Renovate/GitOps (which is also something I miss on the hosts running Docker Compose).
Now the research starts. I know Kubernetes, but I don't know Talos Linux, so there's a lot to read because each Kubernetes deployment has it's own nitpicks. Besides, I need to figure out how to fit this new player in my current environment (CA, DNS, storage, backups, etc).
Will my experience become a series of blog posts? Honestly: most likely not. In a previous poll the majority of people who read my blog posts expressed that they're more interested in Docker/Podman. Besides, the Fediverse is already full of brilliant people talking extensively talking about Kubernetes, so I will not be " yet another one".
You will, however, hear me ranting. A lot.
3/3
The main reason for replacing my Proxmox for a Kubernetes deployment, is because most of what I have deployed on it are LXC containers running Docker containers. This is very cumbersome, sounds really silly, and is not even recommended by the Proxmox developers.
The biggest feature I would miss with that move would be the possibility of running VMs. However, so far I've only needed a single one for a very specific test, that lasted exactly one hour, so it's not a hard requirement. But that problem can be easily solved by running Kubevirt. I've done that before, at work, and have tested it in my home lab, so I know it is feasible. Is it going to be horrible to manage VMs that way? Probably. But like I said, they're an exception. Worst case scenario I can run them on my personal laptop with kvm/libvirt.
2/3
Quick talk about the future of my home lab. (broken out in a thread for readability)
After lots of thinking, a huge amount of frustration, and a couple of hours of testing, I am seriously considering replacing my Proxmox host for a Kubernetes deployment using Talos Linux.
This is not set in stone yet. I still need to do some further investigation about how to properly deploy this in a way that is going to be easy to manage. But that's the move that makes sense for me in the current context.
I'm not fully replacing my bunch of Raspberry Pi running Docker Compose. But I do have a couple of extra Intel-based (amd64/x86_64) mini-PCs where I run some bulkier workloads that require lots of memory (more than 8GB). So I am still keeping my promise to continue writing about "the basics", while also probably adding a bit of "the advanced". Besides, I want to play around with multi-architecture deployments (mixing amd64 and arm64 nodes in the same k8s cluster).
1/3
With that being said: Hello, Cilium.
@OpenSearchProject #Kubernetes Operator v2.8.0 — now officially supporting #OpenSearch 3.x!
- snapshot policy
- warm role
- data streams
- custom labels
- auto update user password on secret change
- improved ISM policy handling
- Go 1.24.4 comptibility
and more.
Check it out:
https://github.com/opensearch-project/opensearch-k8s-operator/releases/tag/v2.8.0
Navigating Failures in Pods With Devices - https://kubernetes.io/blog/2025/07/03/navigating-failures-in-pods-with-devices/ #Kubernetes
Looking to build a Kubernetes administrator career? Start with these 5 steps:
Complete our FREE, Introduction to Cloud Infrastructure Tech (LFS151) course
Next, take our FREE, Introduction to Kubernetes (LFS158) course
Save 40% on your Certified Kubernetes Administrator (CKA) exam when you bundle it with a THRIVE-Annual subscription
Enroll in Kubernetes Fundamentals (LFS258)
Earn your Certified Kubernetes Administrator (CKA) certification
https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/
New blog post: A detailed look at the new network setup
https://blog.transitory.social/posts/2025-07-02-network-rebuild-project/
Almost everything was rebuilt, and multiple layers of complexity were eliminated
#Homelab #Networking #Kubernetes #Mikrotik
If you're using Akamai Cloud, guess what? pgEdge Distributed #PostgreSQL is now available on this cloud vendor (formally known as #Linode) in order to bring performance and availability for #database infrastructure to edge networks.
Read more about our latest partnership on our blog:
https://www.pgedge.com/blog/pgedge-distributed-postgresql-now-available-on-akamai-cloud