Let’s be completely honest: nobody goes into DevOps to memorize CLI flags. Whether you are managing a few development clusters or driving a massive production infrastructure on AWS EKS, the reality of modern GitOps is that you are constantly context-switching. One minute you are debugging a local Helm chart, and the next you are forcing FluxCD to sync a stubborn repository.

When a deployment stalls on a Friday afternoon, you don’t want to dig through pages of official documentation just to find the exact syntax to reconcile a Git repository source.

This post is your definitive, battle-tested quick-reference guide for both Helm and FluxCD. Bookmark it, keep it open in a side tab, and save your brainpower for actual problem-solving.

1. The Essential Helm Cheatsheet

Helm acts as the package manager for Kubernetes. Even in a strict GitOps model where Flux handles automation, you still need Helm locally to lint charts, test templates, and inspect active releases.

Chart & Repository Management

Before you deploy anything, you need to manage where your charts are coming from.

• Add a remote repository:

helm repo add <repo-name> <repo-url>
*Update all local repositories:**
helm repo update

helm search repo <chart-name>

helm install <release-name> <repo-name>/<chart-name> -f values.yaml --namespace <ns>

helm upgrade --install <release-name> <repo-name>/<chart-name> -f values.yaml -n <ns>
**Roll back to a specific previous version:**
helm rollback <release-name> <revision-number> -n <ns>

#Uninstall a release entirely:
helm uninstall  -n

helm template <release-name> <repo-name>/<chart-name> -f values.yaml

#View the user-supplied values of a deployed release:
helm get values <release-name> -n <ns>

**See the history of all revisions for a release:**
    
 helm history <release-name> -n <ns>

2. The Essential FluxCD Cheatsheet

Once you move past manual Helm updates and embrace GitOps, the flux CLI becomes your control center. It allows you to monitor, trigger, and debug the controllers managing your cluster state.

Bootstrap & System Verification

Setting up or checking the health of your GitOps operators.

#Check if your cluster meets Flux prerequisites:
flux check --pre

**Bootstrap Flux onto a GitHub repository:**
    ```bash
    flux bootstrap github \
      --owner=<github-username-or-org> \
      --repository=<repo-name> \
      --branch=main \
      --path=./clusters/my-cluster \
      --personal

Source Management

Sources define where your infrastructure code lives (Git, OCI registries, or S3 buckets).

flux get sources git

flux reconcile source git flux-system

Delivery Control (Kustomizations & HelmReleases)

Flux uses Kustomization (ks) to apply raw manifests and HelmRelease (hr) to manage Helm charts declaratively.

flux get kustomizations

flux reconcile hr <helmrelease-name> -n <namespace>