`agentk` should notify Flux about new OCI artifacts when they are available
Release notes
By default, Flux synchronizes Kubernetes manifests at regular intervals. Triggering a reconciliation immediately when a manifest changes by default requires additional configuration. We recently released automatic Flux triggers on git repository updates using the GitLab agent for Kubernetes. This release provides immediate triggers to Flux when a new OCI artifact is pushed to the GitLab container registry.
Problem to solve
As an Application Operator, I want new deployable images to be picked up immediately by my preferred GitOps tool (Flux), so I don't have to wait for its regular reconciliation loop.
Today, Flux provides incoming webhook receivers that need to be set up to have Flux trigger a sync without waiting for its configured reconciliation loop. Setting up such a receiver is a non-trivial task as it requires a secret and configuration in the cluster and in GitLab.
Not in scope
Cross-project triggers depend on Flux to GitLab access management (#389393) and Manifest projects outside of the Agent configur... (&7704 - closed)
WIP Proposal
Flux needs the OCIRepository or HelmRepository name to reconcile.
Extend the agent config with
- an image name and tag pattern to watch
- the tag matching should support semver
- a name of the Flux resource to trigger the reconciliation for
Recommended workaround
Use the agent CI integration to trigger a Flux sync after the OCI got built and pushed.
Example here: https://gitlab.com/gitlab-org/ci-cd/deploy-stage/demos/podtato-head-delivery/-/blob/main/.gitlab-ci.yml?ref_type=heads#L31
Intended users
Feature Usage Metrics
Extend Metrics for Flux GitOps usage with GitLab (#366294 - closed) with support for OCIRepository and OCI type HelmRepository metrics.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.