fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.6K
active users

#speedcruiser

0 posts0 participants0 posts today
Mika<p>OK, finally got the node back up again. I decided to just get a brand new <a href="https://sakurajima.social/tags/BeQuiet" rel="nofollow noopener" target="_blank">#BeQuiet</a> SFX PSU, to replace the old <a href="https://sakurajima.social/tags/SpeedCruiser" rel="nofollow noopener" target="_blank">#SpeedCruiser</a> Flex PSU and rebuild the node with otherwise the same hardware, into a spare <a href="https://sakurajima.social/tags/Silverstone" rel="nofollow noopener" target="_blank">#Silverstone</a><span> SG13 case I have and it all works.<br><br>Also discovered that the reason why HA wasn't working and none of my VMs I've set replication for didn't carry over to the healthy node was because I had forgotten to actually create a HA group on Proxmox and set the VMs to HA so... did that.<br><br>Now I'm freaking wrestling with my </span><a href="https://sakurajima.social/tags/RKE2" rel="nofollow noopener" target="_blank">#RKE2</a> <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a> cluster to get it back up and running again, cos atm the cluster is littered with pods that are either <code>Pending</code>, <code>Unknown</code> or in a crash loop... which is always fucking fun. Also the cluster itself is kind of slow to respond (on <a href="https://sakurajima.social/tags/k9s" rel="nofollow noopener" target="_blank">#k9s</a><span>)... which is concerning but I think has to do prolly with how its networking is setup.<br><br>I'm still completely clueless honestly on what the "ideal" networking setup is for both Proxmox, and a Kubernetes cluster hosted on Proxmox. I'm still stuck with the defaults, for now, that is using the onboard nic on each Proxmox node for every single thing. The only customisation I've done was setting a bandwidth limit (on Proxmox) </span><b>only</b> for <code>migration</code>. <a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener" target="_blank">#Homelab</a><span> folks please feel free sending some suggestions my way, that is as dummy-friendly as possible :))<br><br>RE: </span><a href="https://sakurajima.social/notes/a2e9fm36yg" rel="nofollow noopener" target="_blank">https://sakurajima.social/notes/a2e9fm36yg</a></p>