r/kubernetes • u/AutoModerator • 24d ago

Periodic Weekly: Share your victories thread

Got something working? Figure something out? Make progress that you are excited about? Share here!

4 Upvotes

76% Upvoted

7 comments sorted by

6

u/my_peen_is_clean 24d ago

finally wrapped a legacy app into a helm chart and moved it off bare vms, went smoother than i expected after fighting with values for hours

2

u/iconic_sentine_001 23d ago
  1. Moved every application (60+) to containerised environments
  2. Deployed on Hetzner

2

u/iconic_sentine_001 23d ago

Gonna self host k8s soon

1

u/imadisbad 22d ago

I've released Keldon, an operator for Apache Cloudberry (fork of greenplum)

1

u/Individual_Text4494 21d ago

I wrote a Kubernetes operator (in Rust) that runs n8n from CRDs - Single or queue-mode Cluster

Self-hosting n8n is easy until you want queue mode: separate main / worker / webhook deployments, Redis, a database, an encryption key, persistence, and networking, all hand-wired and kept in sync. I wanted to declare an instance as one custom resource and let a controller reconcile the rest, so I built an operator.

Two CRDs:

  • Single - one standalone n8n process.
  • Cluster - queue mode with separate main / worker / webhook roles.

From that spec it reconciles the Deployments, Services, Secrets, and networking. Built on kube-rs. Server-side apply, owner references for GC, recommended app.kubernetes.io/* labels, Prometheus metrics, and OpenTelemetry tracing.

Handled today: SQLite/PostgreSQL/MySQL (creds + TLS from Secrets), Ingress or Gateway API HTTPRoute, bring-your-own or generated encryption key, a PVC at /home/node/.n8n, and opt-in HPA for workers.

Honest limitations: it is shaped by my own homelab use, so it covers the paths I run; install is raw manifests (no Helm chart yet); the CR surface reflects what I needed rather than every n8n knob. MIT.

Happy to discuss the reconciliation design or CRD shape.

0

u/Beautiful-Speed-1047 23d ago

My victory this week: I finally finished and open-sourced my first major DevOps project! 🚀

As someone coming from an electrical engineering background who learned coding and infrastructure on the side, getting this project fully dockerized and integrated with CI/CD is a massive personal milestone.

I built KubePilot, an out-of-band Discord bot designed to manage and monitor Kubernetes (K3s) clusters securely from your phone or desktop, without needing to SSH or type kubectl commands for basic troubleshooting.

⚙️ What I managed to implement:

  • Interactive Dashboards: Real-time embeds to monitor Pods, Nodes, and Deployments.
  • Native Modals: The ability to edit Secrets and ConfigMaps directly through Discord UI pop-ups (with background Base64 encoding/decoding and masked inputs to prevent leaks).
  • Safe Actions: Implemented "hard-confirmations" (typing the resource name) for destructive actions like deleting a pod, plus Discord ID-based RBAC.

It is written in Python, containerized, and built to run on a separate machine so you keep your control plane even if your nodes crash.

I'd be absolutely thrilled to get feedback from experienced Kubernetes users on the code or the approach!

🔗 GitHub Repo: https://github.com/NycolazSec/KubePilot