10 years since Google made the first commit in #Kubernetes. And ten years of Google mostly running something else for their own services. I don’t work that much on infra these days, and Kubernetes sure has a fuckton of warts. But I’ve gotta say, compared to what we had before, and the way it transformed the industry… “game changer” is for once not an exaggeration.
I’m interested in running #FrankenPHP (i.e., #Caddy) as the app server for a website. The website has multiple domains pointing to it, and I plan to run this in a #Kubernetes cluster. Can someone point to any docs or blog posts that show how others have set up similar configurations with Caddy or FrankenPHP, especially with regard to how Caddy magically configures HTTPS for the domains in this kind of setup?
Doe je iets met #opensource, #openstandards of #opensystems dan moet je erbij zijn. In november heb je weer een kans, want we organiseren 2x
p/jr een conferentie.
We zijn een vereniging, dus je kan lid worden! Zie: https://nluug.nl
Having to recycle your #kubernetes nodes because the #HPA isn't scaling up your #Mastodon#sidekiq so you're now lagging 15K jobs behind looks like this in the #UI:
Had fun this weekend working on a performance focussed proof of concept using Bunny in the #PHP#queue interop contracts. The first metrics are in using the #RabbitMQ cluster on my #Raspberrypi#Kubernetes home cluster. (Which isn't meant for high performance. Still pleased by these numbers.)
#AlpineLinux is generally my default goto for #kubernetes#container image bases when I'm writing stuff from scratch. I love how lightweight and simple it is, so I'll often start there until I can prove that I need something more complex.
Decided to sit down and try to learn #kubernetes despite the fact that I don't have any real need for it on my little home server. Still, it's been interesting and - I won't lie - a bit frustrating at times. It's very much like using a chainsaw to butter my bread for my use case, but I had a nice feeling of satisfaction when I succeeded in getting #owncast set up through it. I've had some odd issues with Docker failing to launch certain containers through containerd that I have not been able to figure out, however.
I was putting thought into maybe redoing my server setup with kubernetes but I sincerely worry that I'll run into this same containerd issue with some of my other apps.
I managed to avoid #Kubernetes for 10 years, but it’s finally caught up to me, so I hope I’m a Kubernetes god after going through all this required (by job) Kubernetes training.
Energy use of #Kubernetes when it's not doing anything is off the charts. There's about 4 processes that just sit there doing 'something' even when there's zero happening on the cluster. Initialize k8s, start it up and do nothing. Energy being burnt. So if you have less than 8 cores on that box, then it's spamming the scheduler making everything else laggy.
you know hacking kubernetes manifests is so much more comfortable in python... is there any drive to get a yaml processor into the python standard lib?
Trying to automatically/programmatically replicate #DockerCompose stacks on the same host. E.g. I have an application that requires multiple containers, and I want to replicate the WHOLE application with its own volumes, networks, subdomain, etc. Any pointers on how to do that? #Ansible? Please don't say #Kubernetes.
I'm still learning the tools in nicolaka/netshoot, but also need some #dotnet specific things.
I stumbled on the lightrun-platform/koolkits package for node, and I wish they had a #dotnet image -- anyone using anything better than the dotnet-monitor container?