A post about etcd v3, mainly about how paths work in v3.

Today I was playing around with an empty etcd v3 cluster, placing keys with the Golang Library inside it, and I was looking around to get some context on how etcd stores the data. Usually, I need to get an idea of how data is stored before I feel comfortable with the solution. You can view this post as a sort of gist for myself but I hope it can help you too!

Recently I needed to get access to Keybase since I bought the M1 Pro. During the first try to sync the folders in a Keybase team the application hung and refused to copy the secrets to the filesystem. Keybase is allowed to download these secrets, however copying dozens of secrets by hand 1 by 1 is not an option.

After some investigation, I found out that Keybase relies on FUSE to mount the filesystem. According to this topic, it happened more often.

In the previous post, we went through a lot of steps to get Minikube running on the Apple M1 Pro without docker-desktop. Eventually, it was working on a virtual machine with vftool. The problem with this setup is that it would take a lot of effort to get minikube accessible directly from my MacBook.

In the closing words, I already mentioned I had an idea to run Minikube directly on the M1 Pro. In a programming project, I needed an etcd and Kubernetes setup. I already used rancher-desktop, rancher-desktop lacked the etcd setup. The rancher-desktop setup is to run Kubernetes as minimal as possible and etcd is not included, so I had the idea to use Minikube and use its internal etcd cluster to connect my golang project against it.

This year I started my own company: 0to1. To get up and running quickly I decided to stick with technology that I knew before, hardware I have used for the past 8 years without breaking down has been Apple MacBook Pro’s. The new Macbook M1 Pro had raving reviews, super performance, and long battery life.

Knowing that the processor architecture changed from Intel (x86) to ARM (M1), after a year things should certainly have been ironed out… right?

When you install k3s as described on k3s.io, you can run into the following error when you try a kubectl get po without sudo:

Unable to read /etc/rancher/k3s/k3s.yaml, please start server with -write-kubeconfig-mode to modify kube config permissions.
error: error loading config file “/etc/rancher/k3s/k3s.yaml”: open /etc/rancher/k3s/k3s.yaml: permission denied

There are a couple of solutions to run kubectl without sudo on k3s, without the need to reinstall k3s. I will list 2 of them

Today a short share.

Since last year I have been using golang more in my toolkit, often I copy paste but some moments I have to actually write code. For this I use vscode and gopls is the language server.

What is gopls? It stands for Go please. It is a language server and helps linting, autocompleting, adds warnings that this string is not of type []some.thing. It integrates with my favorite IDE: vscode. Fancy stuff. And today was that day that it abandoned me and no longer responded. It did not autocomplete and didn’t give warnings when I used a wrong type. The result is that every iteration I had to run go build to see if the compiler found any issues, the benefit for using a language server is that you get instant feedback. I was slowed down and I cannot have that.

A couple months ago D2IQ (formerly known as Mesosphere) CEO Tobi Knaup announced all their efforts are going towards their Kubernetes offering: https://d2iq.com/blog/d2iq-takes-the-next-step-forward

If you read between all the marketing and management blabla you will find out that DCOS is End Of Life. Since D2IQ was the main contributor of Mesos, one of the core components of DCOS, we can safely conclude that Mesos is losing its main contributor.

As a platform engineer you are asked to help out make developers scale their application, how to make their work easier and more secure. However the specifics on how to make this icon’s background transparent or how to use a clean and sexy font is something that I have very little experience with.

The not-invented-here syndrome is something that is really big in the HPC landscape, since often solutions are not invented yet. And in alot of other software developing fields people tend to first build something before Googling it. In platform engineering however most of the solutions seem to already be there for the day to day task. So when I decided to make a blog I wanted off the shelf products, something easy to maintain, something fast and quick to integrate into existing technology.

After the 4th or 5th time the https://0to1.nl domain hosting company got taken over, the interface seemed to get worse and worse, I decided to move the domain to TransIP. I worked with the TransIP interface before and it is easy to manage, they offer an API and 2FA so my requirements were quickly met.

Every couple of months I register a domain for a project I plan to work on. The end result is hundreds of euros in costs per year for domains I hardly use. Today was going to be different! I registered https://imkerijsoest.nl for my beekeeping hobby and after struggling with setting up Let’s Encrypt on TransIP I was reminded why I registered this domain: To document these steps and share them with the world.

This HOWTO will very likely be out of date soon, since Microsoft updates their Azure portal way too often to make documentation reliable. The official documentation for setting up OpenID in Azure Active Directory was outdated and I could not find a few of the listed options they described on: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-openid-settings. If this documentation can help one or two people with setting this up it would be worth it, since i spend a couple hours on finding the right endpoints and setup i decided to make this HOWTO. In this HOWTO we are going to set up OpenID for DCOS Enterprise. Currently this is all text, since I only have access to Azure through my employer and I do not want to share any details from their accounts.