Technology1 min read

GitOps Promoter: Declare, deploy, deliver

By · Published by Everything Blog

In short

The new Technology Preview release incorporates GitOps Promoter and Source Hydrator to streamline application deliveries. Whenever commits occur, Source Hydrator converts DRY branches into preview branches before Promoter manages pull requests to advance them into deployed branches. Teams configure the deployment sequence using a PromotionStrategy custom resource that supports automated or manual pull request merging. Two-tier gating with proposed and active commit statuses ensures changes pass validation and health checks before progressing.

Key points

  • Promotion sequences are configured via a PromotionStrategy custom resource that allows te…: Promotion sequences are configured via a PromotionStrategy custom resource that allows teams to require human approval or permit automatic merging.
  • Proposed gates directly block pull requests whenever pre-promotion checks like vulnerabil…: Proposed gates directly block pull requests whenever pre-promotion checks like vulnerability scans or manifest validations fail.
  • Active gates halt promotions downstream by ensuring an application maintains healthy post…: Active gates halt promotions downstream by ensuring an application maintains healthy post-deployment conditions in earlier environments.

Sources checked by our analysis pipeline: 1

GitOps Promoter enables you to effectively manage the promotion of your GitOps manifests between environments. Organizations often relied on continuous integration (CI) tools to manage promotions imperatively, GitOps Promoter simplifies the promotion process by enabling a declarative process.

Red Hat OpenShift GitOps 1.22 introduces GitOps Promoter and Source Hydrator as Technology Preview features.

GitOps Promoter overview

The GitOps Promoter, in cooperation with the Source Hydrator, manages the promotion of environments from a don't-repeat-yourself (DRY) branch to preview branches, <env>-next

, to finally the deployed branches <env>

.

The DRY branch contains the manifests you want to deploy and typically uses a YAML management tool like Kustomize or Helm to avoid duplication (hence the DRY moniker). Anytime a commit is made in the DRY branch the Argo CD Source Hydrator automatically hydrates the change simultaneously to the preview branches <env>-next

.

At this point, GitOps Promoter takes over to promote the change from the <env>-next

branches to the <env>

branches by creating and managing pull requests in the Git repository. Any proposed gating defined in the promotion strategy is applied to…

Technology