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:
Ok ok I admit that I recycled my nodes because I could. Kicking the pod probably also would have fixed it but they where up for 82 days and it felt fun
After a few days enjoying the sun on Vlieland, I can say that the most unusual dutch flavour combination that I have tried is mustard with cranberries.
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.)
Thanks to @jay Bunny #PHP will support client properties in the upcoming 0.5.6 and 0.6 releases. Client properties can be used to set a human readable name to your connection with #RabbitMQ:
Doing some #PHP package maintenance tonight, this dev dependency bump kinda stood out ๐ . Mainly I make sure my packages work on the latest #PHP versions, either through support requests or when I run into issues myself. Most of my packages are designed with the future in mind.
The long-term plan is to get reusable workflows for every package and #Renovate to open PR's more aggressively than #dDpendabot to uncover potential future issues. Currently rolling that out with every package I
@ciaran Cool, that looks like a sweet improvement, but how does it compare to Docker on Linux as a baseline? Genuinely interested to know how close they are to closing the gap
@ciaran I'm aware, not expecting a 1:1 comparison. Just a course one would be useful. If this is from a public repo I can run it on a 3 year old Linux machine and a brand now Windows 11 with WSL2 machine if you're interested.
Merged https://github.com/jakubkulhan/bunny/pull/147 earlier today into the 0.6 dev branch. You can test it out with composer require bunny/bunny:^0.6@dev. Looking forward to any feedback on it before releasing bunny/bunny 0.6 in a few months. With the following other changes:
Kinda forgot how much fun it was to write code stitching map tiles together, and also how easy it was. Currently at 82 lines of #PHP. Once finished it will be a new package, as the #golang has some massive glaring bug in it that took me 6 years to find. Sprinkling some threads and #AMQP over this once it's done. The home clusters fans will sing once more
Another reason to run things such as #RabbitMQ as a cluster: If the #Docker image is missing the #arm64 arch one pod will stay pending while the continues working
First part of a new long term home project coming in. An #Ubiquiti PoE+ switch to power a small #Kubernetes cluster built using #raspberrypi nodes. Going to blog about every step once it has been completed. But it is going to be a few quarters long project doing bit by bit
This is my current power supply situation for the cluster worker nodes, #PhilipsHue, and the switch supplemental cooling fan. Not ideal, but perfectly fine if it wasn't in the way of the #lego MOC I've been building around the cluster. So it has to move:
The initial thought was to use this one and put it under the MOC. Except it has 3 ports .... which is problematic because of the bulkyness of one adapter:
So instead I went with this tower, we have the same one downstairs powering the living room #lego display. Plenty of space and nothing will block each other. Plus it comes with 4 #USB powers we will utilize for (more) lego display lights and planned #ESPHome sensors on the stairs to the home office. Just need to pick and time and date as doing this will take that entire switch down, and create a network split between two and one control plane #kubernetes nodes.
The fun part is that I've already accidentally ran with 3 nodes, while I need 4 over the past week occasionally. Tweaked my home brow #kubernetes cluster autoscaler a bit to aggressive and it took out a node while it shouldn't.
Thing is that I used to have a fixed always on #PoE+ node. But changed it so that all of them can be turn on and off. And because it will always turn the longest running off, it's now cycling through all the nodes over time and each one of them gets run down time.
