werf v1.2 features & progress

[shurup]

This discussion will cover the current status of our undergoing efforts regarding the next major release — werf v1.2. It brings a lot of long-awaited features & improvements, so don't miss it!

i'll start with moving here our old posts regarding the progress.

October 8th

There are 3 milestones for this exciting release and we are happy to share details about them:

1. Basic version that will reside in alpha & beta channels only. Its highlights:

• Full Helm 3 support (no more support for Helm 2). No auto-migration from existing Helm 2 installations (will be completed later — see below).
• Revamped machinery for interacting with registries, no more need in specifying stages storage. Related changes include automatic building with werf run & werf converge and elimination of the werf publish command.
• Full migration to content-based tagging. This type of tags solves most of the cases better than other strategies. If you still want to use your own tags, this option will be also available (see below).
• Huge overhaul of werf's website and documentation. Making an easier and more friendly way to introduce werf for newcomers. A short and clear message what is werf on the main page will be followed by Introduction (understand it better in 5 minutes) → "Quickstart" (15 minutes) → "Full guide" (build & deploy your app in a few hours). All other information will be presented in "Reference", "Advanced" and "Internals" sections.
• Improving artifacts' import. Checksum will be calculated for imported data only, not the whole image.
• Noticeable renaming: "signature" will be now known as "digest".

2. Full version that will appear in the stable channel as well. It will introduce new additional features:

• Making werf fully deterministic Git by default (following the GitOps approach). To achieve this, mounts will be available using a specific argument only, env will be in Go-templates inside werf.yaml, Go-templates (in werf.yaml) will be capable to read external files (which are not in Git).
• Local development: new werf compose up command. It is the same as docker compose but with an ability to work with images built by werf.
• Local development: new --follow option for werf run, werf compose up and werf converge commands. It watches for new commits in your local Git repo and restarts containers when needed.
• Pushing charts to registry & deploying from registry.

3. Full+ version (smooth migration from v1.1). It will cover 100% of use cases for those who is currently working with werf v1.1. Notable features include:

• Auto-migration for Helm 2 releases (to Helm 3).
• Custom tags support (in addition to default content-based tagging).
• "Two-pass" mode for the builder. It will require to be explicitly enabled in werf.yaml for specific stages.
• Working simultaneously with multiple registries. One registry can be used for final images only, another local registry — for caching, etc.
• An ability to "export" images to any external registry.

November 9th

• Current v1.2 beta is ready to be used for new projects! Please check out our updated documentation page as well.
• We're busy with implementing new features for v1.2. This version will become stable but it's still not recommended for a seamless migration from v1.1 (due to lack of Helm 2 → Helm 3 auto-migrations). Here are major features that are currently being made:
  • Local development & docker-compose.
  • Pushing charts to chart repository. It will open new possibilities for CI/CD when working with a plenty of microservices. Each microservice can be deployed to the chart repo instead of Kubernetes. Then it can be used by an independent CI/CD mechanism deploying a microservice from the chart repo to Kubernetes.
  • New default operating mode for werf v1.2 with everything fully determined by Git. It will break backward compatibility with projects that use constructions restricted by this mode. In this case, you'll be able to disable the mode by a special option in your werf.yaml.
• Our work on documentation for v1.2 is still in progress. Most recently, we've updated the following pages: Reference / werf.yaml, Reference / CLI and deploy templates in Helm basics.

Please note: while v1.2 can be already used for your new projects with werf, the seamless / automagical migration from v1.1 will be implemented later (using the Full+ version mentioned in the post above).

November 20th

• New operating mode with everything fully determined by Git is available starting from v1.2.1+fix1 release. It implies that:
  • werf.yaml configuration is read from the current Git commit only;
  • .helm/templates templates and other .helm files are read the current Git commit only;
  • Go templates constructions to read files (including .Files.Get and .Files.Glob) can now read data from the current Git commit only;
  • it's forbidden to use mount, git.branch that pulls changes in the external repo's branch, fromLatest.
• Basic local development support becomes available starting from v1.2.1 via:
  • werf compose command (it works like docker compose, the following subcommands are supported at the moment: config, up, down);
  • --follow argument for werf converge, werf run and werf compose up commands. This parameter is used to follow new commits in your local Git and restart relevant containers, converge process, etc.

Please note: when v1.2.1 alpha becomes beta, the backward compatibility will be broken due to switching to the new operation mode (fully determined by Git) by default. We'll announce this change in advance.

[shurup]

December 11th

• Our new operating mode with everything fully determined by Git is now called Giterminism (it stands for Git + determinism). It is enabled by default in alpha starting from v1.2.1.
  • Important reminder: since it's not compatible with current v1.2 beta, the migration of v1.2.1 (from alpha to beta) might break working configurations. We plan to promote this release to beta on Monday (December 14th).
  • We plan to extend the giterminism configuration with additional settings allowing to disable it for specified functions.
• Local development support becomes even better. In addition to the werf compose command and --follow argument, we now also have the --dev flag. When it's enabled, werf starts to take into account the files that are not yet committed but already added to the index (via git add). Give it a try in the alpha channel starting from v1.2.2!

• Helm charts support in v1.2:
  • Subcharts can now be used in the giterminism mode. Two following conditions should be met:
    • Chart.lock should be committed to the Git.
    • You need to vendor your dependencies in advance, via werf helm depdencies build command (not update) before running werf converge. (There is no need to commit downloaded dependencies to the Git; just having your Chart.lock in the Git is fine.)

• We're on the way to implement pushing images & charts to the container registry. Such a set of built images and templates for them will be called a bundle. It will allow you to separate pushing your new release (to the registry) and deploying it (on the cluster).
  • A set of commands to work with such bundles will be implemented: werf bundle publish, werf bundle install/deploy/….
  • Based on that, we're going to create a Kubernetes operator that will automatically deploy werf bundles.

Other changes include:

• Tests are being fixed for v1.2;
• werf dismiss --with-namespace is now working correctly (waiting for the namespace to be removed first);
• Quickstart is now fixed & confirmed to work on Linux, Windows and macOS;
• Not implemented yet but we're going to make automated caching for external images pulled from public Docker registries (think of Docker Hub), so you will have them in your own container registry.

[shurup]

December 18th

Our weekly updates for major werf v1.2 features:

• Local development with the --dev flag:
  • available in v1.2 alpha & beta channels now;
  • various bugs are fixed (including Windows support);
  • now it's covered by tests;
  • submodules & binary files are now supported.
• Pushing & deploying chart bundles. Bundle is a set of built images & Helm templates published in the container registry. The following commands are being developed:
  • werf bundle publish --repo X --tag Y builds required images and pushes a bundle to the repo using the tag. Doesn't require a Kubernetes connection. Availabile in the current alpha;
  • werf bundle apply --repo X --tag Y pulls a bundle (that has been pushed before) and deploys it to Kubernetes;
  • werf bundle export builds required images to make a bundle (Helm-compatible chart) locally (in the specified directory);
  • werf bundle download pulls a bundle (that has been pushed before) and makes a bundle locally (in the specified directory).
• Giterminism ("fully determined by Git" mode) is now in its beta.
  • A new config file called werf-giterminism.yaml and placed in Git has been introduced (Implement fine-grained giterminism config #3046). It will become a successor of WERF_LOOSE_GITERMINISM and WERF_NON_STRICT_GITERMINISM_INSPECTION options to provide you a more fine-grained control of how your files are affected by Giterminism. It should become the last incompatible change in v1.2 related to Giterminism.

Other fixes:

• Dockerfile builder with Giterminism enabled is working correctly now with huge directories excluded by .gitignore.
• werf + Dockerfile now can connect to Docker-server using TCP+tls (remote docker daemon support (Client sent an HTTP request to an HTTPS server.) #2668).
• BuildKit is temporarily disabled for v1.2 ([v1.2, dockerfile] BuildKit is not supported #3028) due to a bug in the Docker's library. (Waiting for our PR to be merged.)

[shurup]

December 25th

• Giterminism (the "fully determined by Git" mode):
  • Most options in the werf-giterminism.yaml file are now supported (Implement fine-grained giterminism config #3046). The few last left will be implemented soon. This config is available in werf starting from v1.2.4 in the alpha channel.
  • The --loose-giterminism option (and the WERF_LOOSE_GITERMINISM=1 environment variable) will be removed in v1.2.4 since werf-giterminism.yaml replaces it. There will be a relevant WARNING if this option is still in use, so you'll have enough time to migrate to werf-giterminism.yaml. Currently, trying v1.2 alpha and its werf-giterminism.yaml is recommended. It is the last incompatible change in v1.2 related to Giterminism.
• Pushing & deploying chart bundles. Using bundles (sets of built images & Helm templates published in the container registry) is available starting from v1.2.3 (in both alpha & beta channels).
  • e2e tests for different container registries implementations are now being implemented.
  • Some issues (i.e. Werf bundle apply does not support subcharts: Error: found in Chart.yaml, but missing in charts/ directory #3058, Werf bundle publish by the same tag does not republish updated chart #3059) are being addressed.
• Other improvements & fixes:
  • timeout for the werf converge command has been fixed: no more "deadline-exceeded" error for it; by default, it's now unlimited instead of 5 minutes (Timeout option when specified breaks werf converge upgrade process with deadline exceeded #3062);
  • Symlinks linking to the files in Git submodules are now supported in the Giterminism mode ([giterminism] Support submodules and symlinks in the giterminism mode #3053).

[distorhead]

January 29th

Early access v1.2 is available!

source $(multiwerf use 1.2 ea --as-file)

There are 2 major features avaiable and ready to use in this ea release:

1. Giterminism (the "fully determined by Git" mode): https://werf.io/documentation/advanced/configuration/giterminism.html .
2. Bundles (sets of built images & Helm templates published into the container registry): https://werf.io/documentation/reference/cli/werf_bundle_apply.html .
   • Bundles not republished by the same version tag is no longer an issue ([bundles] Fix bundle not republished by the same tag #3163).

The next step is v1.2 stable release, which will include following:

• Documentation page about migration from v1.1 to v1.2.
• Builtin werf command to migrate from an existing helm 2 release to helm 3.
• Better giterminism documentation, more detailed reference.
• Basic bundles documentation.
• Support for custom tags for images in the container registry instead of default content-based tags.
• Support resources annotation which will allow setting default replicas field in the .helm/templates when HPA is active (converge 3-way-merge resource updater should not reset replicas field if HPA is active).
• Full support for arbitrary symlinks and submodules for the giterminism subsystem.
• Stabilization and performance fixes when problems will arrive. Looking forward for your feedback and bug reports for v1.2 version.

[distorhead]

Clarification update

Generally there are 3 main major features in the v1.2: giterminism, bundles and local development with --dev flag. While local development was ready to use since december 18, giterminism and bundles are ready to use in the current ea release.

[distorhead]

February 5th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Giterminism (the "fully determined by Git" mode, https://werf.io/documentation/advanced/configuration/giterminism.html):

   • Full support of git-submodules and symlinks.
   • IMPORTANT. Go-templates env "VARIABLE_NAME" function for werf.yaml configuration now requires variable to be explicitly set (more info [config] The env function requires the set environment variable  #3193).
   • Improved errors reporting for uncommitted files (more info [giterminism] Improve feedback and manager logic  #3167).

2. Other fixes and changes:

   • Colored output support for Windows cmd.exe (!).
   • Fixed git service worktree switch procedure occured on every werf run (disabling worktree cache) in Windows due to backslash-slash issues.
   • Added required go-templates function for werf.yaml configuration (more info [config] The required function to declare a variable as required #3194).
   • Support setting initial number of replicas when HPA is active for Deployment (more info Support setting initial number of replicas when HPA is active for Deployment #3195).
   • Fixed usage of strict yaml parser in v1.1 to allow usage of yaml-anchors and duplicate keys int values.yaml files as in standard helm (more info Duplicate key in the values.yaml causes error #2871).
   • Fixed pull-request integration tests not passing, refactored ci to run tests a bit.

What's next:

• Support for custom tags for images in the container registry instead of default content-based tags (draft [build, helm] Custom tags support #3203).
• Migration helper command to migrate from existing helm 2 installation (werf v1.1) to helm 3 (werf v1.2): werf helm migrate2to3 command (draft [helm 2 to 3] "werf helm migrate2to3" command, prevent "werf converge" when helm 2 release exists #3206).
• Better giterminism documentation, more detailed reference.
• Bundles (sets of built images & Helm templates published into the container registry, https://werf.io/documentation/reference/cli/werf_bundle_apply.html):
  • Documentation with detailed explanation and use cases.
• Documentation page about migration from v1.1 to v1.2.
• IMPORTANT Removal of --loose-giterminism flag will occur after ~ February 15th.
• Stabilization and performance fixes when and if problems will arrive. Looking forward for your feedback and bug reports for v1.2 version.

[distorhead]

February 12th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. https://werf.io landing page rework.

2. Fixes for the giterminism (the "fully determined by Git" mode, https://werf.io/documentation/advanced/configuration/giterminism.html):

   • Support .gitignore (more info [giterminism] Fix .gitignore rules are not fully supported #3242).
   • Fix broken symlinks processing (more info [giterminism] Fix broken symlinks are processed incorrectly #3236).
   • Optimize listing of files with globs (more info [giterminism] Optimize listing files with glob #3228).
   • Cache chart dependencies by hashsum of the whole .helm/Chart.lock from the git repo, not digest (more info [helm][giterminism] Cache chart dependencies by hashsum of the whole helm/Chart.lock, not digest #3226).

3. Fixes for bundles (sets of built images & Helm templates published into the container registry): https://werf.io/documentation/reference/cli/werf_bundle_apply.html .

   • Fix "unable to create bundle: unable to write ... no such file or directory" when .helm/templates directory contains subdirectories.

4. Other fixes and changes:

   • Introduced logboek logging library v0.5: https://github.com/werf/logboek/releases/tag/v0.5.0.
   • Fixed werf fails when docker registry contains broken images with BLOB_UNKNOWN errors (+ backported to v1.1).
   • Added support for sprig v3 functions into werf.yaml go-templates of v1.1 werf version. Only those sprig v3 functions have added, that do not exist in the sprig v2 due to compatibility reasons (from/to json/yaml functions are available now in v1.1 🔥).
   • Fixed CRLF issues of stapel builder on windows (more info [win][git] Fix CRLF issues and patch-does-not-apply errors #3241).
   • Added .Values.global.werf.name service value (more info Added .Values.global.werf.name service value with werf cli util project name #3230).

5. Support for custom tags for images in the container registry instead of default content-based tags.

   • This feature has been suspended due to difficulties to implement this with full correctness (more info Add support for custom docker images tags using --add-custom-tag and --use-custom-tag options #3235).

6. Migration from v1.1 to v1.2.

   • Added werf helm migrate2to3 command https://werf.io/v1.2-alpha/documentation/reference/cli/werf_helm_migrate2to3.html.
     • Command will create helm 3 release and adopt existing resources into this release.
     • There is no legal way back to helm 2 after this point.
   • werf converge command detects existing helm 2 release and complains requiring to perform manual migration with werf helm migrate2to3 command.

What's next:

• Automatic migration to helm 3 during werf-converge if chart rendered correctly, fix for v1.1 to prevent werf-converge when helm 3 release is available (draft Auto migrate helm 2 to helm 3 during werf-converge #3245).
• Better giterminism documentation, more detailed reference.
• Bundles (sets of built images & Helm templates published into the container registry, https://werf.io/documentation/reference/cli/werf_bundle_apply.html):
  • Documentation with detailed explanation and use cases.
• Documentation page about migration from v1.1 to v1.2.
• Actualize documentation about CI/CD with werf.
• Actualize documentation about helm.
• "Certified" github actions support for v1.2 and bundles.
• Automatic garbage collection on build-hosts: cleanup git-patches, git-archives, git-worktrees and built docker images.
• IMPORTANT Removal of --loose-giterminism flag will occur after ~ February 15th.

[distorhead]

February 19th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Reworked giterminism documentation (the "fully determined by Git" mode):

   • Reference: https://werf.io/documentation/reference/werf_giterminism_yaml.html
   • Detailed description: https://werf.io/documentation/advanced/configuration/giterminism.html

2. Automatical migration from existing helm 2 release of werf-v1.1 to helm 3 release available in alpha, beta and ea channels.

   • Werf-converge command will create helm 3 release and adopt existing resources into this release.
   • There is no legal way back to helm 2 after this point.
   • Also added helm 3 release existence checker into v1.1 to prevent redeploying your project with v1.1 when it has already been migrated to v1.2.

3. Fixes for bundles (sets of built images & Helm templates published into the container registry): https://werf.io/documentation/reference/cli/werf_bundle_apply.html .

   • Do not render published chart in bundle-publish and bundle-export commands ([bundles] Do not render published chart in bundle-publish and bundle-export commands #3256).

4. Other changed and fixes

   • Added support for --kube-config-base64 cli option (or $WERF_KUBE_CONFIG_BASE64, or $WERF_KUBECONFIG_BASE64, or $KUBECONFIG_BASE64 variable) for v1.2.
   • Added --validate and --include-crds options for werf-render command (Add --validate and include-crds opts for werf-render cmd #3252).
   • Ignore the non-existent --tagging-strategy option for ci-env cmd ([ci_env] Ignore the non-existent --tagging-strategy option #3254).

What's next:

• Bundles (sets of built images & Helm templates published into the container registry, https://werf.io/documentation/reference/cli/werf_bundle_apply.html):
• Documentation with detailed explanation and use cases.
• Documentation page about migration from v1.1 to v1.2.
• Actualize documentation about CI/CD with werf.
• Actualize documentation about helm (draft [docs] Rework advanced/helm documentation chapter (part 1/3) #3266).
• "Certified" github actions support for v1.2 and bundles.
• Automatic garbage collection on build-hosts: cleanup git-patches, git-archives, git-worktrees and built docker images.
• IMPORTANT Removal of --loose-giterminism flag.

[distorhead]

February 26th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Landing page improvements https://werf.io/:

   • new animated into picture;
   • better documentation version selection switch.

2. New bundles (sets of built images & Helm templates published into the container registry) documentation page:

   • en: https://werf.io/v1.2-alpha/documentation/advanced/bundles.html
   • ru: https://ru.werf.io/v1.2-alpha/documentation/advanced/bundles.html

3. Reworked helm advanced documentation chapter:

   • One big helm basics article split into sections, which contains multiple articles.
   • English only for now, Russian coming soon.
   • There is some grammar issues and broken links — fixes coming soon.
   • Reference/helm chapter is planned.
   • Current version though is available at the site: https://werf.io/v1.2-alpha/documentation/advanced/helm/overview.html

4. "What's new in v1.2" documentation chapter:

   • Consists of 2 articles:
     • Changelog: https://werf.io/v1.2-alpha/documentation/whats_new_in_v1_2/changelog.html
       • English only, Russian coming soon.
     • How to migrate from v1.1 to v1.2 guide: work in progress, not available yet.

5. Giterminism (the "fully determined by Git" mode) related internals rework.

   • Use git status command instead of go-git status to optimize checking of uncomitted files and support global .gitignore (more info [giterminism] Switch to the new logic of handling changes in the user's worktree/index #3273).

6. Local development

   • Working on the ways to enable instant synchronization of application source files in the running containers:
     • Using mounts and special werf.yaml configuration section for an image to instruct werf to automatically inject kubernetes host-mount specs into deployed resources.
     • Using rsync server sidecar and tmp-dir + werf-converge in follow mode
   • Trying to find the best solution for guides between k3s, minikube and docker-desktop on different OS-s, this is work in progress for now.

What's next:

• Documentation chapter what's new in v1.2: ru and en versions for migration guide, ru version for changelog, reword changelog.
• Documentation chapter about helm: ru version and fixes for links and grammar, reference for helm directives.
• Actualize documentation about CI/CD with werf.
• Local development improvements and experiments.
• "Certified" github actions support for v1.2 and bundles.
• Automatic garbage collection on build-hosts: cleanup git-patches, git-archives, git-worktrees and built docker images.
• IMPORTANT Removal of --loose-giterminism flag.

[distorhead]

March 5th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Giterminism (the "fully determined by Git" mode) and local development changes:

   • Added --dev-mode=simple|strict flag.
     • simple — read uncommitted/modified files directly from the local filesystem.
       • This mode is default.
       • In this mode werf will not read untracked files.
         • Untracked files should be added once with the git add command`.
         • Some IDE will add untracked files automatically.
     • strict — read only files from the git-index (files which has been added using git add command).

2. Working on documentation.

   • Helm chapter has been refined and translated to russian:

     • en: https://werf.io/documentation/advanced/helm/overview.html
     • ru: https://ru.werf.io/documentation/advanced/helm/overview.html

   • What's new in v1.2 chapter refined and completed.

     • Chapter contains 2 articles: full changelog and short guide how to migrate from v1.1 to v1.2.
       • en: https://werf.io/documentation/whats_new_in_v1_2/changelog.html
       • en: https://werf.io/documentation/whats_new_in_v1_2/how_to_migrate_from_v1_1_to_v1_2.html
       • ru: https://ru.werf.io/documentation/whats_new_in_v1_2/changelog.html
       • ru: https://ru.werf.io/documentation/whats_new_in_v1_2/how_to_migrate_from_v1_1_to_v1_2.html

   • Refined giterminism article: added info about local dev mode.

     • https://werf.io/v1.2-alpha/documentation/advanced/giterminism.html

   • Some refinements for the introduction and reference pages:

     • https://werf.io/v1.2-alpha/introduction.html (added note about giterminism)
     • https://werf.io/v1.2-alpha/documentation/reference/werf_yaml_template_engine.html
     • https://werf.io/v1.2-alpha/documentation/reference/werf_yaml.html

   • Russian page https://ru.werf.io/v1.2-alpha/documentation/internals/build_process.html (actual) is out of sync with the English page https://werf.io/v1.2-alpha/documentation/internals/build_process.html (outdated) — this is planned to be fixed.

3. Reworked internal site infrastructure.

   • Werf site deployed as 2 microservices.
     • Each werf version documentation deployed into the separate Deployment.
     • Main site also deployed into the separate Deployment.
   • This allows speeding up deployment of a new version of the documentation, or site edits.
   • Planning:
     • More stabilization of the new scheme.
     • Local site development configuration.
     • Rework site documentation links and routing.
     • Internal site files refactor to reflect the new site architecture and components separation.

4. Local development research.

   • Planning to implement local development with k3s (considering usage of Docker Desktop for Windows and MacOS).
   • Planning to implement helper command for werf to bootstrap local kubernetes and deploy your application in the local environment seamlessly.

5. Landing page animations refinements will be available soon.

   • Better and more precise animation about werf.
   • Better and more precise animation about how werf works.

6. Found some problems, which will be fixed very soon

   • Bundles publishes secret-values.yaml along other values, which is wrong.
   • Problems with v1.2 and subcharts, when requirements.yaml / requirements.lock older format used.

7. Planning to implement Garbage Collection of git-patches, git-archives, and local built images (in other words v1.2 will automatically cleanup not only container registry but build hosts also).

[distorhead]

March 12th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Github Actions for werf v1.2 are ready to use: https://github.com/werf/actions.

2. Working on documentation.

   • Supported container registries article rework.
     • Available only in russian for now: https://werf.io/v1.2-alpha/documentation/advanced/supported_container_registries.html
     • English translation will be available soon.
     • Added supported registry implementations info into the bundles article.
       • This update will be available soon in the address: https://werf.io/v1.2-alpha/documentation/advanced/bundles.html

3. Working on Garbage Collector for v1.2

   • GC for local images built by the werf (draft [GC] Basic garbage collection for local host built images #3345).
     • Werf v1.2 will automatically cleanup not only container registry but build hosts also.
   • GC for git-archives and git-patches, which are stored in the ~/.werf/local_cache folder coming soon.

4. Bundles and werf-helm-* commands fixes

   • Fixed bunles published .helm/secret-values.yaml and not published .helm/values.yaml (more info [bundles] Fix bundle-publish ignores .helm/values.yaml and uses .helm/secret-values.yaml #3325).
   • Added support for secret files into werf helm * commands (more info [helm] Enable secret-values in 'werf helm *' commands, fix lint command, fix secret-values params priority #3329).
   • Fixed werf helm lint .helm command — this command is usable now (more info [helm] Enable secret-values in 'werf helm *' commands, fix lint command, fix secret-values params priority #3329).

5. Other fixes and changes

   • Fixed .helm/requirements.yaml|lock obsolete files usage: these files are deprecated, but still working now (more info [helm] Add support for .helm/requirements.yaml and .helm/requirements.lock older format #3322).
   • Fixed chart dependencies loader missing errors report (more info [helm] Fix chart dependencies loader missing error reports #3321).
   • Dockerignore-related fixes: consider dockerignore when creating service git-archives (more info [dockerfile] Skip files ignored by .dockerignore file creating a context archive #3343).

6. Internal refactor

   • [git_repo] Use PatchMatcher instead of FilterOptions #3341

7. Internal site infrastructure and CI rework.

   • More site infra refactoring on the way.
   • Added review-environments for PR to check documentation changes (using PR label "review docs").

8. Landing page animations refinements will be available soon.

   • Better and more precise animation about werf.
   • Better and more precise animation about how werf works.

9. Local development research.

   • Planning to implement local development with k3s (considering usage of Docker Desktop for Windows and MacOS).
   • Planning to implement helper command for werf to bootstrap local kubernetes and deploy your application in the local environment seamlessly.

[distorhead]

March 19th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Working on werf site: https://werf.io.

   • Landing page updates.
   • Reworked organization of url's.

2. Working on Garbage Collector for v1.2.

   • Available in alpha, enabled only manually with feature gate: WERF_DISABLE_AUTO_HOST_CLEANUP=false, will be enabled by default soon.
   • This GC can be started manually with the werf host cleanup command.
   • This GC will run automatically in all main werf commands (like werf-converge, werf-build, etc.), and it will try to maintain host clean by deleting:
     • Old /tmp/werf-config-render-* and /tmp/werf-project-data-* files.
     • Old ~/.werf/local_cache/{git_patches|git_archives|git_worktrees|git_repos} data based on LRU algorithm (not available yet, will be released soon).
     • Old werf stages images based on LRU algorithm.
       • NOTE: Werf v1.2 will remove only those v1.1 images, which use container registry as stages storage rather than :local (:local images is legacy and should be cleaned by the werf cleanup command).

3. Git subsystem related fixes, optimizations and refactoring.

4. Updated Docker Client builtin into werf, enabled support for the BuildKit (disabled by default, enabled with the DOCKER_BUILDKIT=1 variable).

5. Other and fixes.

   • Fixed usage of .dockerignore in Dockerfile-builder when creating giterministic context for the docker builder from the current commit.
   • Deprecated --repo-implementation param in the favor of --repo-container-registry param (draft Deprecation warning for the --repo-implementation option #3376).

6. Local development research.

   • Planning to implement local development with k3s (considering usage of Docker Desktop for Windows and MacOS).
   • Planning to implement helper command for werf to bootstrap local kubernetes and deploy your application in the local environment seamlessly.
   • UPD. Succeedeed to run k3s in the local docker server, which will be portable way to run kubernetes locally in any OS.

[distorhead]

March 26th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Working on documentation:

   • Sitemaps.
   • Guides fixes.

2. Working on Garbage Collector for v1.2.

   • Added support for ~/.werf/local_cache git-related data: git-archives, git-patches and git-worktrees: LRU based cleanup.
   • Added support for v1.1 images cleanup into v1.2.
     • NOTE Host cleanup procedure will not be added into the v1.1 version itself, but v1.2 version can remove v1.1's images.
     • NOTE V1.2's host cleanup procedure will remove only those v1.1 images, that has been published into the container registry (--stages-storage=:local images cannot be removed that way, use v1.1 werf cleanup -s :local to cleanup such images per project).
       • --stages-storage=:local is a legacy way to store stages, v1.2 does not support :local storage for images being deployed into the kubernetes and for bundles.
   • Enabled GC host cleanup by default in v1.2 alpha.
   • Will be available in beta and ea very soon.

3. Fixes for v1.1 builder (and v1.2 too) for some cases.

   • Handle cases when container registry contains some broken images (BLOB_UNKNOWN and MANIFEST_UNKNOWN).
     • Added support for images rejection when some image from container registry cannot be pulled.

4. The last feature before stable release: support for caches to store application dependencies in the registry images instead of persistent mounts usage. More details will be available next week.

5. Other and fixes.

   • Added support for directories in contextAddFile directive (also renamed to contextAddFiles, more info Add support for directories in dockerfile contextAddFiles directive #3178).

6. Local development research (NO UPDATES THIS WEEK).

   • Planning to implement local development with k3s (considering usage of Docker Desktop for Windows and MacOS).
   • Planning to implement helper command for werf to bootstrap local kubernetes and deploy your application in the local environment seamlessly.
   • Succeedeed to run k3s in the local docker server, which will be portable way to run kubernetes locally in any OS.

[distorhead]

April 2nd

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. The last feature before stable release: support for caches to store application dependencies in the registry images instead of persistent mounts usage.

   • Experimenting with NFS (unfs3, nfs-ganesha, go-nfs, kernel nfs) to implement the most effective copying of data from container image.

2. Documentation changes and fixes.

   • Actualized cleanup article.
   • Fixed broken quickstart instructions for MacOS.

3. Reworked interface of werf cleanup commands.

   • werf cleanup --repo REQUIRED_REPO;
   • werf purge --repo REQUIRED_REPO;
   • werf host purge [--project-name OPTIONAL_PROJECT];
   • werf host cleanup [--project-name OPTIONAL_PROJECT].

4. Fixes.

   • More fixes for werf v1.2 + helm dependencies: OCI registries support.
   • Automatically reset the Dockerfile exception by .dockerignore file rules (more info [dockerfile] Automatically reset the Dockerfile exception by .dockerignore file rules #3451).
   • Debug and fix images rejection in the case when BLOB_UNKNOWN images found in the container registry (fixed in v1.1 and v1.2).

5. Site infra.

   • Move to ghcr.io github registry implementation, to support running werf.io on containerd.

[distorhead]

April 16th

Stabilizing v1.2. Available in the early-access channel:

source $(multiwerf use 1.2 ea --as-file)

What's new:

1. Working on the last feature before stable release: support for caches to store application dependencies in the registry images instead of persistent mounts usage.

   • Experimenting with NFS (unfs3, nfs-ganesha, go-nfs, kernel nfs) to implement the most effective copying of data from container image.
   • Experimenting with libremotec to share files between containers.
   • Experimenting with LD_PRELOAD and ptrace based mechanics to intercept all syscalls made inside build-container and redirect all reading of files in the /cache to another container over some network protocol.
   • Experimenting with fuse-overlayfs inside docker build container with lowerdir mounted as nfs volume from another container, and upperdir — the new layer for next cache version.

2. Fixed some serious bugs in v1.2:

   • Object-not-found error when using submodules in the project repo.
   • Fixed werf to handle BLOB_UNKNOWN errors from the container registry properly.
     • BLOB_UNKNOWN errors will occur when container registry has been used when GC procedure was active. It is required to switch container registry to the read-only mode when GC procedure is active.

3. Moved away from bintray to yandexcloud based S3 storage.

   • Also we are working on the new way to deliver werf binaries safely using TUF repository.

[distorhead]

June 10th

Project development progress. Still stabilizing v1.2. Fixing critical bugs. Working on werf-guides. Working on a new way to deliver werf binaries using TUF-repository.

Details:

1. Fixed some serious bugs in v1.2:
   • Fixed invalid result of importing from artifacts and images when multiple include-paths has been specified ([stapel] Fix imports with several include paths do not work properly #3555).
   • Fixed werf resources tracker exits before resources are ready.
     • Problem was in kubedog multitracker (Fix multitracker exited before ready issue kubedog#208 and [for werf v1.1] Fix multitracker exited before ready issue kubedog#209).
     • Fix available in v1.1 and v1.2 alpha channels for now.
2. Added support of files renames when adding a single file using git.add=/file git.to=/renamed_file directives.
3. Last feature before stable v1.2 release still in progress: support for caches to store application dependencies in the registry images instead of persistent mounts usage.
   • Experimenting with different ways to implement effective copying of files between images and containers.
4. Working on werf guides:
   • https://ru.werf.io/guides/rails/100_basic.html
     • Reworked most of basic-app chapter (currently only for rails app).
     • Working on real-world apps chapter.
   • Updates will be available in english and for other languages soon.
5. Working on a new way to deliver werf binaries.
   • Werf will be distributed using TUF-repository (https://theupdateframework.io/).
   • More info: https://github.com/werf/vault-plugin-secrets-trdl and https://github.com/werf/trdl.

[distorhead]

October 1st

Project development progress

• Completing the remaining features of werf v1.2
• Switching to the new update manager (trdl) #3674
• Completing the main part of the section "Real-world apps" website#254

Weekly report

1. Almost completed first step in adoption of buildah: allow building of dockerfiles with buildah on any supported by the werf platform (linux, windows and macos).

   • Enable buildah mode with WERF_BUILDAH_CONTAINER_RUNTIME=auto|native-rootless|docker-with-fuse environment variable:
     • native-rootless mode uses local storage and runs only under Linux.
     • docker-with-fuse mode runs buildah inside docker enabling crossplatform buildah support. This mode could be changed later to use podman instead of docker.
   • Continue debugging buildah modes.
   • Feature PR: feat: Build dockerfiles with buildah (basic support) #3735
   • Weekly PR history:
     • feat(buildah): fixes for buildah pkg, added buildah-test cmd #3752
     • feath(buildah): refactor: localize docker server runtime usage in the container-runtime pkg #3755
     • feat(buildah): container runtime interface design plan #3760
     • feat(buildah): container runtime interface design plan (2) #3761
     • feat(buildah): implement new dockerfile-image-builder which uses new container-runtime build-dockerfile interface #3762
     • feat(buildah): refactor container-runtime interface and fix usage of runtime #3763
     • implement DockerServerRuntime.BuildDockerfile #3764
     • feat(buildah): working builds with new docker-server runtime #3765
     • feat(buildah): implement legacy container-runtimes methods #3770
     • feat(buildah): update BuildDockerfile, Tag, Push #3771
     • feat(buildah): fix go-build, do not use gpgme, use opengpg golang impl. instead #3772
     • feat(buildah): werf container-runtime initialization procedure #3773
     • feat(buildah): native buildah implemented; BuildahRuntime updates #3774
     • feat(buildah): more fixes for werf container-runtime initialization procedure; fixed docker-server runtime panics #3775
     • feat(buildah): debug werf-build with buildah container runtime #3776
     • fix(buildah): Inspect returns nil, nil on image not found #3777
     • feat(buildah): debug Buildah container-runtime, fix docker-with-fuse inspect method #3778
     • feat(buildah): docker-fuse-buildah implemented; minor fixes #3779
     • feat(buildah): fix git-archives tar creation procedure to include parent directories of added files #3780
     • feat(buildah): mount host ~/.docker auth config for docker-with-fuse buildah #3781
     • feat(buildah): allow usage of buildah container runtime only with dockerfile type images #3783

2. New article "Managing app's configuration" has been written in russian language (will be translated to english soon):

   • docs: new chapter "configuration" website#259

Planning next week

• Prepare first werf release with buildah included.
  • More debug of buildah with dockerfiles in werf.
  • Run werf-converge with buildah inside Kubernetes to build dockerfiles.
  • Investigating buildah performance more.
• Writing new guide articles: "Running scheduled jobs".

[alexey-igrychev]

October 8th

Project development progress

• Completing the remaining features of werf v1.2
• Switching to the new update manager (trdl) #3674
• Completing the main part of the section "Real-world apps" website#254

Weekly report

1. Experimental feature: Building Dockerfiles with buildah on Linux, Windows, and macOS

   • Activated with WERF_BUILDAH_CONTAINER_RUNTIME=auto|native-rootless|docker-with-fuse since v1.2.26
     • native-rootless mode uses local storage and runs only under Linux
     • docker-with-fuse mode runs buildah inside docker enabling cross-platform buildah support (this mode could be changed later to use podman instead of docker server)
   • Debug and rework of werf and buildah init procedure for native-rootless mode
     • fix(buildah): fix native-rootless buildah mode init procedure #3791
   • Debug werf-build command to work properly with native-rootless mode
     • fix(buildah): debug werf-build with native-rootless buildah mode #3796
   • Restricted usage of buildah mode only to those cases when --repo stages storage used
     • feat(buildah): forbid --repo "" or ":local" for Buildah #3797
   • Reworked building of werf release binaries
     • Use CGO and statical build on linux to allow usage of buildah in native rootless mode
     • Do not use CGO on other platforms: windows and macos
       • feat(buildah): statical werf build experiments #3801
       • feat(build): static CGO build #3804
       • build(buildah): crosscompile #3809
   • Completed performance testing comparing docker with buildah in different modes and platforms
     • Results (native buildah wins): Userspace builds without docker server (buildah) #1618 (comment)
     • Written performance test scripts
       • tests: add Dockerfile perf tests #3800
       • tests: add ContainerRuntime operations time checks when WERF_PERF_TEST_CONTAINER_RUNTIME=1 is set #3803

2. WIP: Adding the tag aliases support feat: custom tags #3706

3. Other activities

   • refactor(helm): rename werf chart name stub "stub_name" to "stubchartname" #3802
   • fix(cleanup): fix "should reset storage cache" error during werf-cleanup and werf-purge #3798
   • fix(dev): submodule changes may not be taken into account #3794
   • fix(dev): deletion of untracked files not taken into account #3792
   • docs: Translate storage_layouts.md into English #3789
   • site(installation): reorder selectors #3795
   • werf dismiss --with-namespace hangs when there is a PVC in this namespace #3766 (comment)
   • Sudden problems with stapel and ansible (apt-key add not working in ansible: expired certificate problem)
     • build(stapel): Actualize stapel and ansible #3810

Planning next week

• Continued experiments with buildah, running in k8s and e2e testing Userspace builds without docker server (buildah) #1618
• Adding the tag aliases support

[alexey-igrychev]

October 15th

Main goals

• Completing the remaining features of werf v1.2
• Switching to the new update manager (trdl) #3674
• Completing the main part of the section "Real-world apps" website#254

Weekly report

1. Adding the tag aliases support feat: custom tags #3706

   • The option --add-custom-tag=TAG_FORMAT sets tag aliases for the content-based tag of each image (can be used multiple times).
   • The option --use-custom-tag=TAG_FORMAT allows using tag alias in helm templates instead of an image content-based tag (NOT RECOMMENDED).
   • If there is more than one image in the werf config it is necessary to use the image name shortcut %image% or %image_slug% in the tag format (e.g. $WERF_ADD_CUSTOM_TAG_1="%image%-tag1", $WERF_ADD_CUSTOM_TAG_2="%image%-tag2").
   • For cleaning, custom tags and associated content-based tag are treated as one:
     • The cleanup command deletes/keeps all tags following the cleaning policies for content-based tags.
     • The cleanup command keeps all when any tag is used in k8s.
   • By default, alias tags are not allowed by giterminism, and it is necessary to use werf-giterminism.yaml to activate options:

     giterminismConfigVersion: 1 
     cli:
       allowCustomTags: true

2. Other activities

   • feat(buildah): communication with insecure registries #3842
   • fix(host-cleanup): "permission denied" errors, do not wipe git-patches on every run #3821
   • fix: WERF_SET_DOCKER_CONFIG_VALUE env variable collision with --set param #3827
   • fix(deploy): possible fix for hanging werf-dismiss #3828
   • fix(deploy): WERF_SET_DOCKER_CONFIG_VALUE not working #3832
   • tests(e2e): test dockerfile build with all container runtimes #3838
   • site: Tune resolver for the TUF router #3839
   • site: Router for download URLs #3824
   • docs: Adding fixes to the Quickstart and Installation in the MacOS section  #3816
   • docs: fix migration to v1.2 guide: use .Values.werf.namespace #3826
   • docs: added warning about usage of --set-docker-config-json-value #3835
   • ci: deploy non-versioned site part only on appropriate changes in main branch #3829
   • build: update werf-builder #3840
   • build: parallelize trdl build #3815
   • build: fix old release building script for multiwerf-release-publisher #3818
   • build(stapel): Actualize stapel and ansible #3810

Planning next week

• Completion of ongoing tasks.
• Switching to the new update manager (trdl) #3674.
• trdl
  • New features.
  • Writing new sections for trdl site:
    • Getting started;
    • Reference;
    • Securiry.

[alexey-igrychev]

October 22nd

Main goals

• Completion and release of werf v1.2
• Switching to the new update manager (trdl) #3674
• Completing the main part of the section "Real-world apps" website#254

Weekly report

1. werf v1.2 stabilization

   • feat: update helm to 3.7.1, provide compatibility with old published bundles #3877
   • feat(buildah): communication with insecure registries #3842
   • tests(e2e): test dockerfile build with all container runtimes #3838
   • fix(custom tags): --use-custom-tag with an image name not work properly #3853
   • fix(build): commit object or packfile not found after git GC #3856
   • fix(stapel): add patch to update ssl certs in the old stapel image #3864
   • fix(cleanup): panic: runtime error: invalid memory address or nil pointer dereference #3870
   • fix(deploy): fix dismiss command fails with "panic: close of closed channel" #3873
   • ci(tests): fix "./gocovmerge: No such file or directory" #3880
   • ci(tests): fix failed workflows #3869
   • "object not found" error in werf-build command #3769

2. trdl stabilization and working on the content of the site trdl.dev

   • feat(server): auto sign all release targets trdl#88
   • feat(server): store trdl-channels.yaml in the default branch by default trdl#84
   • docs(README): update the section Architecture trdl#86
   • chore: shell scripts to work with trdl vault server trdl#77
   • The "Quickstart" section on the site trdl#78
   • The "Security" section on the site trdl#80

3. The main part of the section "Real-world apps"

   • Compile the section "Real-world apps"  website#279
   • docs(rails): translating real apps - assets chapter website#278

Planning next week

• Switching to the new update manager (trdl) #3674
• Working on the content of the site trdl.dev

[alexey-igrychev]

October 29th

Project development progress

• Making GPG signatures for release artifacts by trdl-server.
• Switching to trdl repository in werf actions.
• New translations of guide chapters:
  • Real-world apps/Serving assets
  • Real-world apps/Working with database
  • Real-world apps/Working with files

Activity by areas

1. werf

   • feat: update helm to 3.7.1, provide compatibility with old published bundles #3877
   • Allow usage of user defined helm post-renderers #3862
   • werf build --follow=true --dev is not reacting #3888
   • "object not found" error in werf-build command #3769

2. trdl

   • Making GPG signatures for release artifacts trdl#82
   • Do not write the plugin log to a file trdl#93

3. Switching to the new update manager (trdl) #3674

   • Not using multiwerf in the site deployment #3852
   • Not using multiwerf binaries actions#43

4. "Real-world apps" guide section

   • Compile the section "Real-world apps"  website#279
   • fix(real_apps): better wording for Serving assets website#282
   • Fix typos and inconsistencies in rails guide website#285
   • Translation of chapter "Serving assets" website#274
   • Translation of chapter "Working with database" website#275
   • Translation of chapter "Working with files" website#276

Planning next week

• Switching to the new update manager (trdl) #3674
• New sections on the site trdl#98

[alexey-igrychev]

November 12th

Project development progress

• New translation of guide chapters: Real-world apps/Configuration and secrets.

Activity by areas

1. werf

   • feat: update helm to 3.7.1, provide compatibility with old published bundles #3877
   • "object not found" error in werf-build command #3769
   • Build-time variables specified in werf.yaml not passed with buildah #3858

2. trdl

   • WIP site: Reference section trdl#108
   • WIP New sections on the site trdl#98
   • WIP https://github.com/werf/trdl/issues/91
   • Redesign CLI trdl#105
   • Ability to disable client self-update trdl#104
   • Error: unable to update tuf meta: tuf: failed to decode timestamp.json: expired at 2021-10-30 09:32:34 +0000 UTC trdl#102

3. Switching to the new update manager (trdl) #3674

   • WIP feat: try to use trdl instead of multiwerf in 'use' and 'update' commands multiwerf#112
   • WIP Releasing a new version of multiwerf that uses trdl under the hood multiwerf#110

4. "Real-world apps" guide section

   • WIP Groom laravel example website#307
   • WIP A new framework in the "Real-world apps" guide section: Node.js website#286
   • WIP Compile the section "Real-world apps" (en) website#316
   • WIP Partial templates for the section "Real-world apps" (en) website#317
   • Completing the main part of the section "Real-world apps" website#254
   • Compile the section "Real-world apps" website#296
   • Partial templates for the section "Real-world apps" website#289

Planning next week

• Switching to the new update manager (trdl) #3674
• New sections on the site trdl#98
• Ongoing tasks

[alexey-igrychev]

November 19th

Project development progress

• The version of multiwerf that uses trdl under the hood is being tested on internal projects.
• Known helm problems with three-way merge solved, bringing changes to upstream.

Activity by areas

1. werf

   • WIP Installation script #3932
   • Broken helm3 three-way-merge case #2 #3462
   • Broken helm3 three-way-merge case #1 #3461

2. trdl

   • Arbitrary path for storing trdl_channels.yaml trdl#119
   • Arbitrary path for storing trdl.yaml trdl#118
   • Release and versioning of the vault plugin along with the client trdl#92
   • Adding "trdl remove" command trdl#81

3. trdl.dev

   • WIP The "Quickstart" section on the site trdl#78
   • WIP The "Security" section on the site trdl#80
   • The "Reference" section on the site trdl#79
   • Add favicon to the site trdl.dev trdl#85

4. Switching to the new update manager (trdl) #3674

   • WIP Releasing a new version of multiwerf that uses trdl under the hood multiwerf#110

5. Guides

   • WIP The section "Deployment best practices" website#330
   • A new framework in the "Real-world apps" guide section: Node.js website#286
   • Compile the section "Real-world apps" (en) website#316

Planning next week

• Switching to the new update manager (trdl) #3674
• New sections on the site trdl#98
• Building with Buildah
• Effective work with git shallow clone

[alexey-igrychev]

November 26th

Project development progress

• The version of multiwerf that uses trdl under the hood is released.

Activity by areas

1. werf

   • WIP Buildah support for stapel builder #3936
   • WIP Running werf in buildah mode in containers and Kubernetes #3933
   • WIP Research running buildah in kubernetes #3951
   • WIP Investigate and rework werf dependencies when using builtin buildah #3950
   • WIP Linting with golangci-lint #3898
   • Installation script #3932
   • Links to binary files in release message #3897

2. trdl

   • WIP The "Security" section on the site trdl#80
   • The "Quickstart" section on the site trdl#78
   • Key expiration date monitoring trdl#135
   • Links to client binary files in release message trdl#117

3. Switching to the new update manager (trdl) #3674

   • Releasing a new version of multiwerf that uses trdl under the hood multiwerf#110

4. Guides

   • Support for multiple snippets with snippetcut_example website#329
   • The section "Deployment best practices" website#330

Planning next week

• Switching to the new update manager (trdl) #3674
• New sections on the site trdl#98
• Building with Buildah

[alexey-igrychev]

December 3rd

Project development progress

• Version werf 1.2 stable has been released. 🎉🎉🎉
• Instructions for running werf in Docker and Kubernetes:
  • Run in Docker.
  • Run in Kubernetes.
  • Use GitLab CI/CD with Docker executor.
  • Use GitLab CI/CD with Kubernetes executor.

Activity by areas

1. werf

   • WIP Transferring the nonversioned part of the site to werf-guides repository #3851
   • WIP Running werf in buildah mode in containers and Kubernetes #3933
   • Instructions for running werf in Docker and Kubernetes #3984

2. trdl

   • WIP Recommended GPG quorum signature creation flow trdl#155
   • WIP The "Security" section on the site trdl#80
   • WIP Quorum of GPG signatures in Quickstart trdl#148

3. Guides

   • WIP Guide chapter layout improvements website#272
   • WIP Translation of the section "Best Practices for deploying" website#347
   • WIP Translation of the section "Real-world apps" for Node.js website#349
   • Translation of the section "Real-world apps" for Laravel website#351
   • Change the domain of the application website#297

New topics for next week

• Comparison of Giterminism with GitOps, as well as werf with its closest analogs.

[alexey-igrychev]

December 10th

Project development progress

• Distributing images with werf to build with Buildah in Kubernetes (read more here).
• Instructions for running werf in Docker and Kubernetes (second edition)
  • Run in Docker.
  • Run in Kubernetes.
  • Use GitLab CI/CD with Docker executor.
  • Use GitLab CI/CD with Kubernetes executor.
  • How it works.

Activity by areas

1. werf

   • WIP Prepare container or host system for running werf in Buildah mode via install.sh #4000
   • Running werf in buildah mode in containers and Kubernetes #3933
   • Transferring the nonversioned part of the site to werf-guides repository #3851

2. trdl

   • WIP Recommended GPG quorum signature creation flow trdl#155
   • WIP The "Security" section on the site trdl#80
   • Quorum of GPG signatures in Quickstart trdl#148
   • Links to vault plugin binary files in release message trdl#151

3. Guides

   • WIP Guide chapter layout improvements website#272
   • Translation of the section "Real-world apps" for Node.js website#349
   • Translation of the section "Best Practices for deploying" website#347

[alexey-igrychev]

December 17th

Project development progress

Diving into GitOps, GitOps solutions, as well as other nearby werf alternatives.

Activity by areas

1. werf

   • WIP Builtin werf cr login/logout commands #3060
   • Warn user if outdated multiwerf detected #4033
   • Deprecate v1.1: add deprecation message when running werf v1.1 build/deploy #4031

2. werf website

   • WIP Guide chapter layout improvements website#272
   • Add README.md and CONTRIBUTING.md website#87
   • Change the default branch from master to main website#280
   • Provide instructions for preparing machine for werf in Buildah mode website#389

3. trdl

   • WIP Recommended GPG quorum signature creation flow trdl#155
   • WIP Translation of the article "Security"  trdl#163
   • WIP Translation of the article "Quickstart" trdl#149
   • The "Security" section on the site trdl#80

[alexey-igrychev]

January

Project development progress

Activity by areas

1. werf

   • Implement dependencies between images #4124
   • Commit info (hash, data) are natively available during deploy and build #4122
   • Multi-stage does not work properly with build args #3938
   • Virtual merge commit related "patch does not apply" #3349
   • feat(gc): run host garbage collection in background #4079
   • feat(werf.yaml): support [[ namespace ]] param in the helm-release template #4078
   • fix(quay): ignore TAG_EXPIRED broken tags #4101
   • fix: 'werf helm get-release' command panic #4089
   • fix(git): fast, ad-hoc fix, return exec.ExitError from gitCmd.Run() #4076
   • fix(git): git warnings sometimes break werf #4071

2. werf website

   • WIP A new framework in the "Real-world apps" guide section: Spring Boot website#410

3. trdl

   • WIP Proofreading and improving the home page  trdl#174

New topics

• ArgoCD/ArgoRollouts integration #4115

[alexey-igrychev]

January 31 to February 13

Project development progress

• Local development just got better
• Delivery in our projects got safer

Activity by areas

1. werf

   • WIP ArgoCD/ArgoRollouts integration #4115
   • Unexpected cleanup fail when getting metadata for custom tag with long name #4134
   • Stages created in dev-mode are not reused after commit #4113
   • Confirm the release and the publication of release channels by a quorum of GPG signatures #4112

2. trdl

   • WIP Proofreading and improving the home page  trdl#174
   • WIP Add examples of adding and removing trusted GPG keys to Quickstart trdl#175
   • WIP Site reorganization trdl#186
   • Confirm the release and the publication of release channels by a quorum of GPG signatures trdl#176
   • test(e2e): quorum verification trdl#180
   • fix(client): unknown flag --home-dir trdl#187

[alexey-igrychev]

February 18th

Project development progress

Activity by areas

1. werf

   • WIP ArgoCD/ArgoRollouts integration #4115
     • feat(bundle): new command "werf bundle render" #4174
     • feat(bundle): add werf argocd cmp sidecar image #4193
   • Cleaning up artifacts by git history-based policy as well as images #4163
   • Odd warning during cleanup: could not parse reference #4166
   • Dependency graph for images in werf.yaml #4168
   • fix(host-cleanup): procedure not running in gitlab-ci #4197
   • fix(host-cleanup): host cleanup not working without --docker-server-storage-path option #4198
   • fix(build): "unable to switch worktree" in gitlab #4177
   • fix(build): werf does not reset stages storage cache when import source image not found #4192

2. trdl

   • Add examples of adding and removing trusted GPG keys to Quickstart trdl#175
   • WIP Proofreading and improving the home page  trdl#174
   • WIP Site reorganization trdl#186

[alexey-igrychev]

March 18th

Project development progress

• Autocleaning of old werf releases within trdl use/update
• Runtime caching instead of stages storage cache on the synchronization server

Activity by areas

1. werf

   • Allow passphrase-protected ssh-keys specified using --ssh-key option or from default location #2134
   • Broken --ssh-key option #1948
   • Broken 3 way merge case: resource not removed after rename and failed deploy #4191
   • WIP feat: new command werf kube-run #4257
   • feat(build): speeding up with runtime caching for meta images  #4247
   • feat(build): speeding up with runtime caching for stages #4255
   • feat(cleanup): optimization of cleaning images which are used when importing #4217
   • feat(deploy): support server side validation in converge/dismiss commands #4229
   • fix: more correct handling of storage.ErrBrokenImage #4199
   • fix: panic when auto host cleanup runs in some werf commands #4205
   • fix(helm): don't add annotations and labels to *List Kinds #4206
   • fix: support WERF_KUBECONFIG_BASE64 in werf-cleanup command #4210
   • fix: WERF_KUBE_CONFIG and WERF_KUBECONFIG environment variables not working #4215
   • fix(buildah): support Dockerfile builder target param to build specific stage #4220
   • fix(deploy): fix server side validation false positive failure case #4237
   • fix: broken --ssh-key option #4240
   • fix: server dry-run validation breaks helm 2 to 3 transition #4244
   • fix(build): do not store images into final repo when --skip-build is set #4246
   • fix: default ~/.ssh/id_rsa key not loaded #4249
   • fix(purge): fix final repo stages deletion #4254
   • docs: werf with ArgoCD experimental CI/CD setup documentation pages #4248
   • refactor: add werf-cleanup command warning when no kube configs available #4213
   • build: update to helm v3.8.0 #4233
   • build: up version of buildah and containerd #4234

2. trdl

   • MacOS: Self-update failed: unable to update tuf meta: tuf: no root keys found in local meta store trdl#210
   • feat(client): autoclean old downloaded releases trdl#200
   • fix(client): autoclean ignores releases downloaded by previous trdl versions trdl#203

[alexey-igrychev]

April

Delivery guild

The werf developers and the DevOps teams at Flant work closely: any engineer can ask for help in the werf chat room. This way, engineers can solve problems related to delivering customer applications faster. We felt that this interaction could be even closer and more productive, so we created the delivery guild. For now, it's just an experiment (we'll see how it goes).

The guild includes experienced engineers from different teams as well as werf developers. Every week, they discuss various pressing issues related to the projects as well as to werf development. The down-to-earth goal of the guild is to jointly develop best practices and prioritize the development of features concerning specific tasks within the Flant ecosystem. The global goal is to balance the planned werf evolution and the development of essential features that are in demand from customers and the community.

Project development progress

• The pre-alpha version of the Stapel image building using Buildah: basic support for all Buildah-based build stages has been implemented. We are currently switching some in-house werf projects to this mode.
• The new werf bundle copy command can copy bundles and related images from one container registry to another.
• You can now use the content-based tag with the new %image_content_based_tag% shortcut when exporting images and creating custom tags.
• The long-awaited function for rendering individual chart manifests, werf render [-s=<glob> ...], is now available.
• Several new werf.yaml directives for managing cleanup policies have been implemented:

  cleanup:
    disableKubernetesBasedPolicy: <bool>
    disableGitHistoryBasedPolicy: <bool>
    disableBuiltWithinLastNHoursPolicy: <bool>
    keepStagesBuiltWithinLastNHours: <unit>