You can easily start using werf for deploying your projects via the existing Helm charts since they are fully compatible with werf. The configuration has a format similar to that of Helm charts.
werf includes all the existing Helm functionality (the latter is built into werf) as well as some customizations:
- werf has several configurable modes for tracking the resources being deployed, including processing logs and events;
- you can integrate images built by werf into Helm chart’s templates;
- you can assign arbitrary annotations and labels to all resources being deployed to Kubernetes globally with cli options;
- werf reads all helm configuration from the git due to giterminism which enables really reproducible deploys;
- also, werf has some more features which will be described further.
With all of these features werf can be considered as an alternative or better helm-client to deploy standard helm-compatible charts.
Briefly, the following commands are used to deal with an application in the Kubernetes cluster:
- converge — to release an application;
- dismiss — to delete an application from the cluster.
- bundle apply — to release an application bundle.
This chapter covers following sections:
- Configuration of helm to deploy your application into kubernetes with werf: configuration section.
- How werf runs a deploy process: deploy process section.
- What is release and how to manage deployed releases of your applications: releases section.