My completely automated Homelab featuring Kubernetes

• k8s_gateway

  3 271 7.3 Go

  A CoreDNS plugin to resolve all types of external Kubernetes resources

  

Technically I am running k8s_gateway which is just coredns with a plugin since there's a FreeBSD binary on the releases page.

• home-ops

  52 1,723 10.0 Shell

  Wife approved HomeOps driven by Kubernetes and GitOps using Flux

My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• flux2

  83 5,927 9.2 Go

  Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.

  

Deployments: (GitOps with Flux)

• renovate

  114 15,732 10.0 TypeScript

  Universal dependency automation tool.

  

Container and Helm chart updates: (Github PRs created by Renovate)

• volsync

  6 456 9.6 Go

  Asynchronous data replication for Kubernetes volumes

  

Volume Backups and Recovery: (VolSync backing up to S3)

• cluster-template

  63 1,540 9.9 Python

  A template for deploying a Kubernetes cluster with k3s or Talos

  

Using Kubernetes and GitOps has been pretty niche but growing in popularity. If you have the hunger for learning k8s or bored with docker-compose/portainer/rancher, or just want to try I built a template on Github that has a walkthrough on deploying Kubernetes to Ubuntu/Fedora and deploying/managing applications with Flux.

• external-snapshotter

  4 433 8.8 Go

  Sidecar container that watches Kubernetes Snapshot CRD objects and triggers CreateSnapshot/DeleteSnapshot against a CSI endpoint.

  

VolSync is a much better option than Velero IMO, Velero was created before GitOps was a thing and it really tries to do too much when all I need is a reliable way to backup and restore PVCs. If your CSI supports volume snapshots, VolSync can use the snapshot-controller to create Volume Snapshots and then mount those as a PVC to a temporary pod to then backup that up to S3. This is really great for backing up PVCs because it's not backing them up from a running workload.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• kanister

  2 722 9.7 Go

  An extensible framework for application-level data management on Kubernetes

  

You could write a k8s cronjob around prodrigestivill/postgres-backup to dump a database backup to an nfs mount or also check out kanister.

• rook

  51 11,905 9.9 Go

  Storage Orchestration for Kubernetes

  

I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.

Suggest a related project