My plan for this afternoon was to finish my centralized reusable #GitHub Actions workflows for releasing projects. But some outage is keeping me waiting 😅. (Can even see the self hosted runners spin up but not getting any jobs.)
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.)
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.
