Brock Henrie

When you need to create a helm application for Argocd to deploy a Helm chart, it can feel a little confusing.

You go to a docs page and read thier installation guide and all you see is

Example: Traefik

helm repo add traefik https://traefik.github.io/charts
helm repo update
helm install traefik traefik/traefik

Where do you even begin?

How does this map to the argocd CRD?

How do I add a values file, I'm just getting an error?

Why is it looking in the helm charts repo for my values file?

When doing a homelab, it starts to get hard to manage multiple deployments to different hosts.

I really like using Gitops and having as much as my infrastructue in code as possible. Tools like terraform and ansible are great for that, but when it comes to just managing containers I haven't found a great way of doing that. If you're talking about single node docker hosts.

Portainer is a great setup but it didn't feel great managing files that I wanted to bind into my container.

I tried Ansible, i just had issues with it removing labels I no longer wanted on the container.

It feels like a lot of overhead, but using K3s and Argocd felt like the best solution. But what are we talking about, its a homelab. Is there too much overhead???

Absolutely Not!

I like to use my homelab to push my boundaries and learn new ways of doing things.

Managing secrets in Kubernetes is hard.

You either...

• Hard code secrets insecurely
• Add a manual process, whether that's scripting or running commands one at a time
• Deploy and maintain a secret management service(s)

Updating services and rotating secrets now takes an eternity just to do something that should take 5 minutes.

We’re going to take you from a hard-coder to a pro coder in no time.

If you want to handle secrets in Kubernetes like a pro, follow along.

First, we’re going to start with the hard, painful way. Then, we’ll bring it up a notch with some automation. Finally, we'll handle it like a pro with a full GitOps-driven approach.

When developing locally, it's often useful to have a self-signed SSL certificate for localhost. This allows you to test your site with HTTPS without needing to purchase a certificate and avoid having to go through the invalid certificate screen.

This guide will show you how to create a self-signed SSL certificate for localhost using OpenSSL and add it to your trust store.

Goose is a Database migration tool written in go. It allows you to make sequential migrations that you can step forward and backward through your db versions.

This allows your migrations to follow Gitops.