feat: publish config/ as an OCI manifests artifact for Flux#56
Draft
TeddyAndrieux wants to merge 1 commit into
Draft
feat: publish config/ as an OCI manifests artifact for Flux#56TeddyAndrieux wants to merge 1 commit into
TeddyAndrieux wants to merge 1 commit into
Conversation
Publish the deployment manifests (this repo's config/ tree) as an OCI artifact Flux can consume directly (OCIRepository + Kustomization), alongside the operator image, so GitOps deployments can pull a versioned bundle. build.yaml is split into a `tags` job that computes the version (+ optional `latest`) and two jobs that consume it: `operator-image` builds and pushes the controller image, `manifests-image` runs `make push-manifests`. Both run on every build, not only on release. The manifests artifact always pins the controller image at the specific version it was built for - even its `latest` tag re-tags the same artifact - so the bundle never drifts from the image across releases. The Makefile gains a `REGISTRY` variable (so `IMG` and `MANIFESTS_IMG` share the ghcr namespace), a self-contained `flux` tool target, and a `push-manifests` target, grouped in a dedicated section separate from the operator-sdk scaffolding. The README documents the artifact with a Flux deployment example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Publish the deployment manifests (the
config/tree) as an OCI artifact alongside theoperator image, so Flux can deploy crl-operator directly from the registry (no checkout):
ghcr.io/scality/crl-operator:<version>ghcr.io/scality/crl-operator-manifests:<version>Changes
.github/workflows/build.yaml: split into atagsjob (computes the version + optionallatest) and two jobs that consume it —operator-image(controller image, unchangedbuild-push-action) andmanifests-image(make push-manifests). Both run on every build,not only on release.
Makefile: aREGISTRYvariable (shared byIMGandMANIFESTS_IMG), a self-containedfluxtool target, and apush-manifeststarget, grouped in a dedicated section separate fromthe operator-sdk scaffolding.
README.md: documents the artifact with a Flux deployment example.Notes
The manifests artifact always pins the controller image at the specific version it was built for
— even its
latesttag re-tags the same artifact — so the bundle never drifts from the imageacross releases.