I've been working on the infrastructure for Launchpad023. Everything declaratively configured because servers should be cattle not pets.
I've put it up on Codeberg if anyone wants to take a look.
https://codeberg.org/launchpad023/launchpad023-infra
#kluctl #kustomize #metallb #talosLinux #selfhosting #kubernetes #envoy_gateway #externalsecrets #stalwart #JMAIL #haarlem
So edge nginx > proxy_pass > tunnel > routed into the compute network. proxy_pass and any other method im aware of needs an IP target, which means using #metalLb or something else that implements LoadBalancer and manages IPAM.
MetalLb last time I used it was actually v nice and worked well by giving it an ip range to work with.
Keeping the nginx config in sync with the services can probably be mostly set and forget but that feels like dumpster fire kindling
2/2
Катастрофоустойчивый Kubernetes: как использовать балансировщик MetalLB с BGP-anycast
Клиенты часто спрашивают, как построить геораспределенный и катастрофоустойчивый
Had an incredible session with #ClaudeCode yesterday debugging why my #homelab #k8s ingress was having trouble after every restart.
It went through my #argo/#helm config, used cli tools like arp etc, ran #netshoot on specific nodes etc to finally diagnose it as an #metallb stale arp cache problem.
Just watching it go through the diagnostics was sometimes so educative!
Using claude code (or any llm client agent for that matter) for infra troubleshooting is underrated!
Kubernetes: шестимесячный марафон по прокачке dBrain.cloud
За последние полгода наши инженеры проделали значительную работу по развитию и оптимизации платформы dBrain.cloud , ключевым инструментом которой является Kubernetes. В этой статье мы подробно расскажем об изменениях, произошедших в инфраструктуре, о внедрении новых функций и фишках, которые, мы надеемся, будут интересны DevOps-сообществу.
https://habr.com/ru/companies/dbraincloud/articles/931798/
#gpu #slicing #s3 #cilium #metallb #ipam #cgroup_v2 #kubernetes #dbrain #devops
Den här bilden säger kanske inte så mycket, men vad den försöker säga är att jag lyckats sätta upp MetalLB i hemmaklustret och exponera min CoreDNS server till det lokala nätverket. Hurra!
Next upp hade det varit based AF om jag kunnat få en IPv6 address också för att slippa gå igenom min proxy när jag inte är hemma.
#K8s #Kubernetes #CoreDNS #DNS #Homelab #Selfhosted #Selfhosting #MetalLB
Well that was an interesting one to debug... My blocky DNS service was down after a cluster restart
A given #metallb speaker won’t advertise the service if:
- the service has externalTrafficPolicy=local and there are no running endpoints on the speaker’s node
To use externalTrafficPolicy=local, the tolerations on metallb pods must match the tolerations on the destination pods
For once it wasn't DNS!
General concepts MetalLB’s purpose is to attract traffic directed to the LoadBalancer IP to the cluster nodes. Once the traffic lands on a node, MetalLB’s responsibility is finished and the rest should be handled by the cluster’s CNI. Because of that, being able to reach the LoadBalancerIP from one of the nodes doesn’t prove that MetalLB is working (or that it is working partially). It actually proves that the CNI is working.
sherbang
Hey Gus
Habr
Sandip Bhattacharya ☮️
Mika
mattlqx
Alex o_O
Gilgwath
beyondwatts