Cees-Jan Kiewiet 
handful times an hour.
On the other side of that coin, I don't want it to get hot at all because it's still held together by #LEGO. Which can held a maximum of 80 degrees celsius according to: https://t.co/bP2FxZX8hx
But judging by the mention of Polycarbonate for transparent bricks could be interesting as well, at least for the contact points with the Pi. *runs off to the pick a brick page*
Ow, another neat detail is that before letting this node join the cluster. I only had to turn it on once, to get the MAC address of the board. It booted straight from USB after that 😍
Resetting the cluster to apply the PoE+ hat fan speed changes, one SSD at a time. And yes at this point I ran a USB cable from my desktop to the cluster because taking the SSD's off would be a hassle:
Ow before I forgot, here is the article by #geerlingguy that taught me how to tweak the PoE+ fans: https://t.co/IorNUhLt0F
#geerlingguy So far, so good (Also installed LongHorn again since the cluster now has 3 nodes. (Hence the spike in temperature in the middle.)):
#geerlingguy After this wipe of the cluster was done, and all nodes were back up. It took 15 minutes for #terraform to reprovision every service running on the cluster: https://t.co/cfnhZvXfAo
And the fan speed tweak really worked out. It gets a tad hotter, but no more annoying spin ups of the cooling fan all the time anymore:
Ok, another big milestone reached, deploy a project to both my #Kubernetes clusters at the same time. This one builds a VPN between both clusters:
Ok, this might look like exactly the same thing as the previous tweet. But this time for my current #Kubernetes cluster #Terraform crafted the kubeconfig that was used to do the deployment. Refs: https://t.co/CYBqnPqQFb
Also terraforming my current cluster will secure it more, plus make a lift and shift, or booting up a clone in another region a lot simpler. (Application specifics excluded.)
Did the boring thing today and added #traefik as ingress, showing my default backend here using a global ingress:
#traefik Was hoping to use #soloio_inc's Gloo instead of #traefik, but no arm64 images available by default made it, for now, an easy call go with #traefik. (Nothing against #traefik FYI, just want to experiment with Gloo more on this cluster.)
Another important milestone today. Started preparing to move an existing project over to use #RabbitMQ on the cluster instead of running on my #Synology NAS. Went all in and set up a 3 node cluster. Up next is configuring the ingress for AMQP
#RabbitMQ #Synology Been iterating over that thing, and have been duping from traffic from the one running on my NAS to see how it works with more than one node: https://t.co/mDtpYwdG6n
And so far #LongHornIO has been invaluable for (insights about) the persistent storage for each pod:
And one of the cats somehow managed to race through the cluster and somehow take out the master node. (It's still running but all network is down.)
Found the cause of the master outage. Deathwing somehow managed to disconnect the SATA to USB adapter from the SSD used for storage so the node didn't come back up after powercycling it.
Here is something interesting I didn't notice yet. The spikes you see are the other two nodes frantically attempting to reconnect with the master node:
Had a chat with #deathwing_t_cat today after I caught him attempting to be a chaoscat again:
My lego order with special parts for a, hopefully, more stable construction also finally shipped yesterday. So early next week more experiments are starting :D!
Right, so the lego parts haven't arrived yet. But the next 3 PoE+ hats for the next 3 nodes did!
Another thing that came in are two USB extension cables. Mainly got those to experiment with less tension on the USB <=> SATA cable
And the big frames to the right might be come a key part in making #LEGO node blades:
Made scale model pillars with diagonal beams for sturdiness but still some movement possible (had bigger ones with the green bars but didn't take a photo), for connecting the blades to:
Had another go at this tonight, and managed to get the RPI and SSD into the cube. Not perfect but getting there 😎
It was interesting to see the amount of traffic flowing through the cluster: https://t.co/IqhxR1XEwE
But sadly had to declare it dead after ETCD decided it ran out of storage: https://t.co/LEmDZxPyGw
So preparing (with k3d) for a triple master cluster, S3 backup and snapshot and automatic recovery before starting it again. Will then do a series of chaos engineering tests to make sure it's resilient against power outages etc etc.
The triple master set up will have each master node on a different switch (!!!) (or access point). Mainly because one of the masters will replace my Raspberry Pi 1 that reads information from the smart meter in this house. The other extra master will have a special purpose.
The meterkast (utility closet) node casing and storage just came in. Never realised M.2 SSD's are so, tiny 😱
Yay! The fine folks at #LEGO_Group seem to have caught up with the custom bricks orders after the holidays zerg 🎉. So I can put together the node #lego enclosures in a few days and start the cluster back up.
Still going for the 3 master setup in the long term, but since I can already start it up with a single master going to focus on building and testing power outage and recovery testing. Hopefully including having a fresh node every time it starts, including the master 🤐
This is a first for me! #LEGO_Group put the custom bricks order in a box 😱. Building the node kube's tonight 🎉. Probably powering the cluster back up next week, and hopefully the more space between components should make it require less active cooling
Hah, progress! But seems I'm missing parts, connector pegs to be specifically so I can't do anything at the moment. Good thing I ordered 200 of those the other day. Might need a few more parts, so another #lego order will go out soon 🤣. But really loving the progress here 😍
Started prototyping a #Kubernetes node with a screen. Next steps are starting X and a browser in kiosk mode
Another big milestone. A new RPI 4 8GB came in, so I can start assembling the utility closet master node:
It's been a decade of two since I had to do configuration through jumpers
There is only one issue. Doing rapid rebuilding of the cluster to test things out is going to be a lot harder because this one won't be as easy to access as the others currently are...
Got it up and running at least https://t.co/0s4snsqtBh and while I love the #argon_forty casing I still think defaulting to using the USB3 instead of the USB2 port will leave plenty of users with I/O issues.
#argon_forty All the nodes in my #k8s cluster run on SSD's on the #USB v2 port because the v3 port has stability issues. Couldn't even write the image to the M.2 #SATA #SSD using the v3 port. Hence the extension cables to hook it to the v2 port. So it has a tail:
But at least I now have two leader nodes, and I'm getting errors like this during some #terraform calls:
Whoop whoop, the #LEGO parts I ordered 6 weeks ago just came in! Time to finish the current enclosures and start with building the tower to put them in
The end result of tonight's thinking with the new #lego parts that came in. Fully hanging node enclosure with room to make it more blade-like/slide it in and out for easy maintenance but that is for another time. Plus the black technic baseplates are amazingly solid <3
The end result for tonight, it is not perfect, and there should be another set of parts arrive in two weeks, but we're getting there. Going to have to order more baseplates tho, those things are awesome and will make the whole project stable af.
Had a small set of #LEGO pieces come in a few days ago. And I finally managed to get a good and sturdy solution for the SSD, and also the RPI, which was a bit tricky with the SSD already in it. Making it about 90% done, the final thing I really want is a way to slide it in and
the enclosure tower. Because maintenance with everything fixed in place will be messy.
And that is the 3rd TF apply done. The (almost) full cluster back up in 3 commands and about 30 minutes of waiting for everything to be installed and back to running:
Next up is rook as a potential replacement for longhorn to use NFS/ISCSI for storage instead. Longhorn is really cool, but with my current number of cluster reinstalls I'm looking for something easier to recover data with
The day ends with only two running because I don't need more, so why would I
Realised today that I could just stack all 3 into one tower above each other. Like the intended result:
Martin 
@wyri when will the first rpi5 node join the cluster? 😆