k8s-HomeOps

Core Components

• actions-runner-controller: Self-hosted Github runners.
• cert-manager: Creates SSL certificates for services in my Kubernetes cluster.
• external-dns: Automatically manages DNS records for my cluster.
• metallb: Bare-Metal Load-balancer implementation.
• ingress-nginx: Ingress controller to expose HTTP traffic to pods over DNS.
• synology-csi: The official Container Storage Interface driver for Synology NAS.
• sops: Managed secrets for Kubernetes, Ansible and Terraform which are commited to Git.
• tf-controller: Additional Flux component used to run Terraform from within a Kubernetes cluster.
• volsync and snapscheduler: Backup and recovery of persistent volume claims.
• system-upgrade-controller Automatically updates kubernetes based off of a plan.

GitOps

Flux watches my kubernetes folder (see Directories below) and makes the changes to my cluster based on the YAML manifests.

The way Flux works for me here is it will recursively search the kubernetes/apps folder until it finds the most top level kustomization.yaml per directory and then apply all the resources listed in it. That aforementioned kustomization.yaml will generally only have a namespace resource and one or many Flux kustomizations. Those Flux kustomizations will generally have a HelmRelease or other resources related to the application underneath it which will be applied.

Renovate watches my entire repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged Flux applies the changes to my cluster.

Directories

This Git repository contains the following directories under kubernetes.

📁 k8s-home-ops
├── 📁 kubernetes                 # kubernetes configurations
│   ├── 📁 apps                   # applications
│   │   └─ 📁 network             # namespace folder
│   │      └─ 📁 cert-manager     # application folder
│   ├── 📁 bootstrap              # bootstrap procedures
│   ├── 📁 flux                   # core flux configuration
│   └── 📁 templates              # re-useable components
└── 📁 infrastructure             # infrastructure configuration

Cluster layout

Below is a a high level look at the layout of how my directory structure with Flux works. In this brief example you are able to see that authentik will not be able to run until cloudnative-pg is ready, which itself requires rook-ceph-cluster to be ready

flowchart TD
  id01>Kustomization: cluster] ==>|Creates| id02>Kustomization: cluster-apps]
  id02 ==>|Creates| id06>Kustomization: cluster-apps-rook-ceph]
  id02 ==>|Creates| id07>Kustomization: cluster-apps-rook-ceph-cluster]
  id02 ==>|Creates| id08>Kustomization: cluster-apps-cloudnative-pg]
  id02 ==>|Creates| id09>Kustomization: cluster-apps-authentik-database]
  id02 ==>|Creates| id10>Kustomization: cluster-apps-authentik]
  id06 ==>|Creates| id11(HelmRelease: rook-ceph-operator)
  id07 -.->|Depends on| id06
  id07 ==>|Creates| id12(HelmRelease: rook-ceph-cluster)
  id08 -.->|Depends on| id07
  id08 ==>|Creates| id13(HelmRelease: cloudnative-pg)
  id09 -.->|Depends on| id08
  id09 ==>|Creates| id14[PGCluster: pg-authentik]
  id10 -.->|Depends on| id09
  id10 ==>|Creates| id15(HelmRelease: authentik)

Loading