Retro Board Update

Well after a couple of months of coding ive got about 50% through doing reto-board, major progress has been made, it is now techniclly possible to sign up for it,

you can’t yet make any boards, but there an example version of what a board will look like non of the functionality works in the example

it took quite a while for me to get the login to work, and the main reason to that is undocumented bits that I had to get working myself, for example “can I do this / userAllowed” is not a standard feature it seems at least not in the golang libraries for keycloak, so I had to go down a very long and winding path

K3OS

K3OS is kinda self explanitory if you know what K3s is, if not then k3OS is Rancher’s k3s which is a kubernetes compatible version but a lot smaller

Why did I tell you that

Well now that bit is out of the way, I upgraded ubuntu on one of my raspberry pi 3’s, and at the same time upgraded k3s to the latest version, and that pi became almost impossible to use with kubernetes, pods failing all the time,
since I needed to wipe it anyway, and possibly replace with a pi4 (which are harder to find than rocking-horse-{redacted}) why not give k3os a shot, this is where the fun began

Issue

So you are already using RancherDesktop and NerdCTL from the betas congrats, but you want to use the multi-platform build

so you need to update Rancher and Nerd, well thats where the issue exists, Lima doesnt update NerdCTL automatically so you need to update your instances version

Fix

First you need to get into the instance

LIMA_HOME=/Users/<username>/Library/Application\ Support/rancher-desktop/lima \
	/Applications/Rancher\ Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl \
	shell 0 sudo --preserve-env=CONTAINERD_ADDRESS sh

Now that your in the instance, you need to update NerdCTL

Integrating Vault with 1Password in Kubernetes

I decided that I should probably get a real handle on my passwords and secrets in kubernetes, since kubernetes is not very good at keeping secrets

So I don’t generally take a helm chart or kube-schema at face value, this has more to do with I prefer to keep things in their own namespace rather than in “default”, because of this I tend to clone the chart first

Well I made Kubernetes cluster using Raspberry PIs, I largely followed the guide RasperryPI 4 Cluster

It has the following features

• 5 Raspberry Pi 4s, 4Gb RAM
• 1 DualCore x64, 16Gb RAM
• 1 DualCore x64, 4Gb RAM
• 4Tb storage distributed over the whole cluster
• ClusterCTRL, this is so power goes through the backplane rather than having 5 seperate power sources

Things that are using the cluster, well this site for one

Well I’ve decided that I should probably learn kubernetes, so I built a raspberry pi cluster

Home

Well I finally pulled the plug and bought a Planck,

rather than build my own though I went with a Planck EZ also rather than buy 1 like any sensible person, when it costs nearly 300 quid, I bought 2

and because obviously I’m npt to be trusted I decided to flash one and learn Workman, I have a couple of firmwares if anyone else is insane like me

Workman this layout is workman, but also moves the numbers on the upper layer to a reverse T pattern is the easiest way to explain it

I decided that I should stick all my aliases and functions that I use into a zsh plugin, that way I can maintain it separately

Github

Home

Progress has been slow to start with, but that should now speed up

I have finished the authorizer, and moved the storage system to Postgres from Dynamo, the main reason for that is that a lot of the data is relational so it makes sense to put it in a relational database

Nest

This is the service where all CRUD operations take place, it is also what triggers Hive

Hive

This is the service that works out what to do with a bug, is it a new one, has it happened before, is it happening frequently, it also triggers the notification system

I have decided to go back to BugFix.es and re-start development

mainly this is due to me needing a common bug/issue tracking system (this is not a ticket system like jira)

BugFix.es tracks bugs, so if a bug is sent to the system and it hasn’t been seen before or was seen a long time ago, or is happening a lot in a short period of time it creates a ticket / notification so development on it can be tracked/done