Introduction

Lovenet Home Operations Repository

Managed by Flux, Renovate and GitHub Actions 🤖

Kubernetes Cluster Information:

         

Overview

This is the configuration for my GitOps homelab Kubernetes cluster. This cluster runs home software services for my residence. It is quite complex and there are a lot of interdependencies but the declarative nature of GitOps allows me to manage this mesh of code. The software services fall into a few primary categories:

• Home Automation (Home Assistant, ESPHome, Node-Red, EMQX, ZWave JS UI, Zigbee2MQTT)
• Home Metering and Monitoring (Weather Station, Power Monitoring, Sensors)
• Home Security (Frigate, Double Take)
• IOT Devices (WLED, Ratgdo)

Core Components

Infrastructure

• CentOS 9 Stream: Kubernetes Node Operating System.
• crun: Container Runtime implemented in C.

Networking

• cilium: Kubernetes Container Network Interface (CNI).
• cert-manager: Creates SSL certificates for services in my Kubernetes cluster.
• external-dns: Automatically manages DNS records from my cluster in a cloud DNS provider.
• ingress-nginx: Ingress controller to expose HTTP traffic to pods over DNS.
• Cloudflared: Cloudflare tunnel client.

Storage

• Rook-Ceph: Distributed block storage for peristent storage..
• Minio: S3 Compatible Storage Interface.
• Longhorn: Cloud native distributed block storage for Kubernetes.
• NFS: NFS storage.

GitOps

• Flux2: Declarative Cluster GitOps
• actions-runner-controller: Self-hosted Github runners.
• sops: Managed secrets for Kubernetes which are commited to Git.
• Rennovate: Automated Cluster Management.

⚙️  Hardware

Network

Click to see a high level physical network diagram

☁️ Cloud Dependencies

Initialization

./init/create-cluster.sh (on master)

./init/prepare-cluster.sh (on laptop)

./init/initialize-cluster.sh (on laptop)

ssh root@master1 rm /etc/kubernetes/manifests/kube-vip.yaml (on laptop)

Teardown

./init/destroy-cluster.sh (on laptop)

Debugging

• https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
• https://dnschecker.org
• https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/
• https://github.com/nicolaka/netshoot
• https://www.redhat.com/sysadmin/using-nfsstat-nfsiostat

Github Webhook

kubectl -n flux-system get receivers.notification.toolkit.fluxcd.io generates token URL to be put into github.com -> Settings -> Webhooks -> Payload URL

• Content Type: application/json
• Secret: <token from kubectl -n flux-system describe secrets github-webhook-token>
• SSL: Enable SSL verification
• Which events would you like to trigger this webhook?: Just the push event.
• Active:

Notes

To get metrics-server to work with kubeadm, you need to do the following if it isn't setup with the clusterconfig provided to kubeadm https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#kubelet-serving-certs

• Need to pull the kubeadm configuration into this repository

Resources: Limits and Requests Philosophy

In short, do set CPU requests, but don't set CPU limits and set the Memory limit to be the same as the Memory requests.

• CPU Guidance
• Limits Guidance

@whazor created this website as a creative way to search Helm Releases across GitHub. You may use it as a means to get ideas on how to configure an applications' Helm values.