Post cover image

February 4, 2025

Just Set Up a Kubernetes Cluster? Here’s What You Actually Need Next

So, you’ve got your Kubernetes cluster up and running. Maybe you installed it with Talos, kubeadm, or some other method. Now you’re staring…

By Mr.PlanB

3 min read

So, you've got your Kubernetes cluster up and running. Maybe you installed it with Talos, kubeadm, or some other method. Now you're staring at it, wondering: What do I actually need to do next?

You'll find a million guides online, all throwing a bunch of tools at you — some useful, some total overkill. The key is to only add what you actually need instead of installing a bloated stack that makes your life harder.

Let's walk through the essentials that'll make your cluster functional, reliable, and easier to manage without overwhelming you.

1. Storage: Where Do Your Persistent Files Go?

If you're running databases (Postgres, MySQL, MongoDB) or anything that needs persistent storage, you'll need a storage solution. But which one?

  • Local Path Provisioner — Quick and easy, but no high availability (HA).
  • Longhorn — Good for HA storage, simple to set up.
  • Rook/Ceph — Powerful but complex, best if you have dedicated resources.
  • SeaweedFS — Lightweight, with built-in S3 support.
  • OpenEBS — Good if you want more control over how storage is handled.

If you're just getting started and don't need HA right now, go with Local Path Provisioner or Longhorn and upgrade later when you feel the pain of needing something better.

2. Ingress: How Do You Expose Services?

You need an Ingress controller to make your apps accessible from the outside world. Your main choices:

  • NGINX Ingress — Solid, reliable, and widely used.
  • Traefik — Easier to configure, supports Let's Encrypt natively.
  • Ambassador — Built on Envoy, great for microservices.
  • Cilium — If you're into eBPF and need advanced networking.

For most setups, NGINX is the best choice unless you have a specific reason to go another route.

3. SSL Certificates: Don't Skip This

If you're exposing services, you'll need HTTPS. Cert-Manager automates SSL certificate generation with Let's Encrypt, so you don't have to worry about renewing them manually.

Easy setup with Helm:

helm repo add jetstack https://charts.jetstack.io
helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --set installCRDs=true

Once installed, you just need to create an Issuer or ClusterIssuer to start automatically generating SSL certs.

4. Monitoring: See What's Actually Happening

A fresh Kubernetes cluster is basically a black box. You need monitoring and logging to know what's happening under the hood.

Start with: ✅ Metrics Server — Basic CPU & memory metrics. ✅ Prometheus + Grafana — The gold standard for monitoring. ✅ Loki — Lightweight logging system for Kubernetes.

Skip the fancy tools for now — just get Metrics Server and Prometheus-Grafana running.

5. GitOps: Stop Manually Applying YAML Files

Manually deploying YAML files is fine at first, but long-term, you'll want automation. GitOps tools help you manage Kubernetes configurations using Git.

  • ArgoCD — Has a nice web UI, good for teams.
  • FluxCD — Lightweight and works well with existing Git workflows.

Pick ArgoCD if you like a UI, otherwise FluxCD is a great alternative.

6. Secrets Management: Don't Hardcode Credentials

Kubernetes' built-in secrets aren't encrypted by default, so if you're storing API keys or passwords, you need something better.

  • Sealed Secrets — Encrypts secrets before storing them in Git.
  • Vault by HashiCorp — Enterprise-grade but complex.
  • External Secrets Operator — Syncs secrets from cloud providers.

For a simple setup, go with Sealed Secrets.

7. Backups: Because Things Will Break

At some point, something will go wrong. When it does, you'll be glad you set up backups.

  • Velero — The go-to tool for Kubernetes backups.
  • Kasten K10 — More features, but requires a paid license.

Just install Velero early so you don't have to learn it after disaster strikes.

8. DNS: Automate Your Domain Names

If you're using cloud DNS services (like Route 53 or Cloudflare), External-DNS will automatically create and update records when you deploy apps.

helm repo add bitnami https://charts.bitnami.com/bitnami
helm install external-dns bitnami/external-dns --namespace kube-system

Now your DNS records update automatically when you create an Ingress. No more manual updates!

Start Small and Build as You Go

It's easy to fall into the trap of installing everything, but Kubernetes is already complex.

Start with: Storage_ (Local Path, Longhorn) Ingress (NGINX, Traefik) Cert-Manager for HTTPS Metrics Server + Prometheus-Grafana Sealed Secrets for security _GitOps (ArgoCD or FluxCD)

Everything else? Wait until you actually need it.

Don't Overthink It

Kubernetes isn't just about installing cool tools — it's about making sure your workloads run smoothly. If you focus on solving real problems rather than just installing what people recommend, you'll build a cluster that's lean, efficient, and easier to maintain.