Our great sponsors
-
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
A mono repository for my home infrastructure and Kubernetes cluster which adheres to Infrastructure as Code (IaC) and GitOps practices where possible
My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
Deployments: (GitOps with Flux)
-
Container and Helm chart updates: (Github PRs created by Renovate)
-
Volume Backups and Recovery: (VolSync backing up to S3)
-
flux-cluster-template
A community opinionated template for deploying a single Kubernetes cluster with Ansible and Terraform backed by Flux, SOPS, GitHub Actions, Renovate and more!
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
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.
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
You could write a k8s cronjob around prodrigestivill/postgres-backup to dump a database backup to an nfs mount or also check out kanister.
-
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.
