werf new feature: Improved Custom Resources tracking and custom status rules (v1.2.272+)

[shurup]

Briefly

Custom Resources tracking has been significantly improved. You can add tracking for any Custom Resource.

This feature became available starting from werf v1.2.272, which is currently in the Alpha release channel.

Background & details

werf uses its sister project called kubedog to track Kubernetes resources. Its last releases, v0.10.0 and v0.11.0, got many enhancements, such as new high-level concurrent dynamic tracker, lots of new generic conditions for the generic tracker, more status conditions, extra case options for conditions, and a separate file for user-contributed resource status rules.

Practically, this makes it much more likely that werf will find fields in the Custom Resources suitable for tracking their readiness (thanks to a vastly extended set of universal rules).

If the Custom Resource you are interested in stores its state in a field that werf could not guess automatically, you can add support for that CR to werf.

Configuration

Refer to the tracker/generic/contrib_resource_status_rules.yaml file to see an example of custom rules allowing werf to track the deployment process of PostgreSQL performed by Postgres operator for Kubernetes by Zalando. Feel free to open your PRs with new tracking rules added.

Additional details

• kubedog v0.11.0 changelog