werf CLI
CLI for full-cycle CI/CD to Kubernetes: image builds, Helm-based deploys and container registry cleanup
- 4,738 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Deploys to Kubernetes and deletes images from the registry
- Requires cluster and registry credentials
Install
- Works in
Manual install
Install werf following https://werf.io/getting_started/ and use https://werf.io/docs/ when configuring builds and deploys. Show me the planned changes before deploying to a cluster.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Deploys to Kubernetes and deletes images from the registry
- Requires cluster and registry credentials
This is third-party code. Review the repository files before installing.
What it does
werf builds and publishes container images, deploys applications to Kubernetes, distributes release artifacts and cleans up the container registry. Configuration uses familiar Dockerfiles and Helm charts, while werf adds build caching, content-based tagging and resource tracking during deploys. It plugs into any CI system and relies on Git, Buildah and Helm.
Who it is for. DevOps engineers and developers building application delivery to Kubernetes.
Good fit when
- You want one tool for building and deploying to Kubernetes
- You need build caching and content-based image tags
- The registry keeps growing and needs regular cleanup of old images
- An agent has to prepare CI/CD config for a project with a Dockerfile and a Helm chart
Not a fit when
- The application is not deployed to Kubernetes
- You only deploy existing charts without builds: Nelm or Helm is simpler
Example request
Prepare werf.yaml and GitLab CI steps to build our Dockerfile and deploy the Helm chart to stagingLimitations
Built around Kubernetes and the Git, Dockerfile and Helm stack. Detailed installation and setup live on werf.io, not in the README.
How to disable. Remove the werf binary or drop the werf steps from your CI configuration.
FAQ
Is there a Russian-speaking community?
Yes, besides the werf_io chat the README lists the Russian-speaking Telegram chat werf_ru.
Is werf production-ready?
According to the README, werf has been used in production since 2017 and is a CNCF Sandbox project.
How is werf different from a Docker and Helm combo?
werf covers the full CI/CD cycle in Kubernetes with one CLI: it builds and publishes images, deploys the app through Helm, distributes release artifacts and cleans the container registry. Configuration builds on familiar Dockerfiles and Helm charts.
How do I install werf and where are the docs?
Install steps and guides are in the official werf docs at werf.io. The catalog lists a werf skill for Claude Code, Codex and Cursor that helps an agent with configuration. Risk is high because werf deploys into a cluster.
Discussion
No questions or reviews yet.
Related
CLI toolsA Helm alternative for deploying charts to Kubernetes with release plans, resource tracking and encrypted secrets
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
An open-source Kubernetes UI with a built-in MCP server: the agent inspects the cluster, diagnoses breakages and operates it with RBAC in mind
A CLI for bulk port forwarding of Kubernetes services to your local machine, with an MCP integration for AI assistants
Container by Aerovato
Container
A CLI for persistent per-project Linux workspaces in Docker or Podman that keep the agent away from the rest of your system
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
README in short
werf is a CNCF Sandbox CLI for full-cycle CI/CD to Kubernetes. It manages the application lifecycle from image builds to registry cleanup. It builds on Git, Dockerfile, Helm and Buildah, with build caching and enhanced resource tracking. Documentation and guides for Node.js, Spring Boot, Django, Rails and Laravel are published on werf.io.