helm
Helm is a package manager for Kubernetes that allows defining, installing, and upgrading applications via charts.
What this skill does
# helm
## Purpose
Helm is a package manager for Kubernetes, enabling users to define, install, and upgrade applications using charts. It simplifies managing Kubernetes resources by packaging them into reusable templates.
## When to Use
Use Helm for deploying and managing applications on Kubernetes clusters, especially when handling multiple environments, versioning dependencies, or automating deployments. Ideal for DevOps workflows involving microservices, where consistent application packaging is needed, such as in CI/CD pipelines for scalable apps.
## Key Capabilities
- Package applications as charts, which are directories containing YAML manifests and templates.
- Support for chart repositories, allowing versioned storage and retrieval.
- Templating engine to customize deployments with values files (e.g., YAML format for overriding parameters).
- Rollback and upgrade features for managing release lifecycles.
- Integration with Kubernetes RBAC for secure operations.
## Usage Patterns
To use Helm, first ensure Kubernetes access via `kubectl` or set the `KUBECONFIG` environment variable (e.g., `export KUBECONFIG=~/.kube/config`). Initialize Helm with `helm init` if needed, then add repositories and install charts. For custom deployments, create a chart with `helm create mychart`, edit values.yaml, and install. Always specify the namespace with `--namespace` flag for multi-tenant clusters.
## Common Commands/API
Helm operates via CLI commands; no direct REST API exists, but it interacts with Kubernetes API server.
- Install a chart: `helm install myrelease stable/nginx --set service.type=LoadBalancer --namespace dev`
- Flags: `--set` for inline overrides, `--values` for external YAML file (e.g., `helm install --values values.yaml`).
- Upgrade a release: `helm upgrade myrelease stable/nginx --set replicas=3`
- Use `--atomic` for rollback on failure.
- List releases: `helm list --all-namespaces`
- Delete a release: `helm uninstall myrelease --namespace dev`
- Search repositories: `helm search repo nginx`
Code snippet for a basic values.yaml file:
```
replicaCount: 2
image:
repository: nginx
tag: latest
```
To add a repository: `helm repo add stable https://charts.helm.sh/stable`, then update with `helm repo update`.
## Integration Notes
Helm integrates with Kubernetes tools; ensure your cluster is accessible via the Kubernetes API. For authentication, use `$KUBECONFIG` for client certificates or tokens. In CI/CD (e.g., GitHub Actions), run Helm in a container with `kubectl` installed: set env var like `export HELM_REPOSITORY_CONFIG=repo.yaml`. For Terraform integration, use Helm provider: define in HCL as `resource "helm_release" "nginx" { name = "myrelease" chart = "stable/nginx" set { name = "service.type" value = "LoadBalancer" } }`. Avoid conflicts by using Helm's `--wait` flag with Kubernetes operators.
## Error Handling
Common errors include "chart not found" (fix by running `helm repo update`), permission issues (ensure RBAC via `kubectl create clusterrolebinding`), or failed hooks (check with `helm status`). For deployment failures, use `helm history release-name` to review revisions, then rollback with `helm rollback release-name 0`. If a chart install errors due to invalid values, validate YAML first with a linter like `yamllint values.yaml`. Always check Kubernetes events with `kubectl get events --namespace dev` for root causes.
## Concrete Usage Examples
1. **Install a WordPress chart**: Add the repo with `helm repo add bitnami https://charts.bitnami.com/bitnami`, then install: `helm install mywordpress bitnami/wordpress --set wordpressUsername=admin --set wordpressPassword=$WP_PASSWORD --namespace web`. This deploys WordPress with custom credentials; ensure `$WP_PASSWORD` is set as an env var for security.
2. **Upgrade an existing MongoDB release**: First, install with `helm install mymongo bitnami/mongodb --set auth.enabled=true`, then upgrade: `helm upgrade mymongo bitnami/mongodb --set resources.requests.memory=512Mi --namespace db`. This scales resources; monitor with `helm status mymongo` to verify.
## Graph Relationships
- Related to: kubernetes (core dependency for deployments)
- Co-located in: devops-sre cluster (shared with tools like kubectl, terraform)
- Tagged with: helm, kubernetes, package-manager (links to similar skills in the cluster)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.