Basics

Perfect 👍 You want the same practical daily-use cheat sheet but for Helm. Here’s a structured list like the Git one — covering install, upgrade, rollback, diff, repo management, etc.


🧭 Helm Daily Commands Cheat Sheet


🔹 Basics

  • Check Helm version

    helm version 3.18
  • Show help

    helm help

🔹 Chart Repositories

  • Add repo

    helm repo add bitnami https://charts.bitnami.com/bitnami
    # here bitnami bitnami here = repo name (alias/identifier you give locally)
    Helm repository URL 
  • List repos

    helm repo list
  • Update repo (fetch latest charts)

    helm repo update # add latest version of charts and repo
  • Search charts

    helm search repo nginx # u will see bitnami nginx related chart

🔹 Install & Upgrade

  • Install a release

  • Upgrade (or install if not exists)

  • Set inline values


helm get

  • Scope: Looks at a release already installed in your cluster.

  • Purpose: Fetches information about a deployed release.

helm show

  • Scope: Looks at a chart (local or remote repo), not the cluster.

  • Purpose: Displays chart metadata, templates, or default values before install.

🔹 Release Management

  • List all releases

  • Get release status

  • Get release values

  • Get all manifests applied

  • History of release (with revisions)


🔹 Rollback & Delete

  • Rollback to previous version

  • Uninstall release

  • Uninstall and delete history


🔹 Debugging & Diff

  • Template (render manifests without applying)

  • Dry-run (simulate install/upgrade)

  • Diff changes (requires plugin)


🔹 Chart Development

  • Create a new chart

  • Lint a chart

  • Package a chart

  • Push chart to repo (OCI)


🔹 Useful Daily Shortcuts

  • Upgrade with forced recreation

  • Check resources in release namespace

  • Delete failed release and reinstall


✅ This list covers 90% of daily Helm usage: installing, upgrading, rollback, debugging, managing repos, and chart development.

Pavan, do you want me to also make a side-by-side comparison table (command vs purpose) for Helm, like we discussed for Git? That way you’ll have a ready interview/cheat-sheet reference.

Last updated