feat: Publish CRDs as a kustomize bundle - #18
Merged
Conversation
Add a publish workflow that pushes config/crd as an OCI kustomize bundle to ghcr.io/datum-cloud/network-kustomize on every push and on release, matching the pattern used in compute and other datum-cloud repos. This lets downstream consumers pull the CRDs via Flux without vendoring YAML. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
scotwells
approved these changes
Aug 21, 2026
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
2 participants
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.
Summary
There was no way for downstream consumers to pull this repo's CRDs without vendoring the YAML. A new publish workflow pushes
config/crdas an OCI kustomize bundle toghcr.io/datum-cloud/network-kustomizeon every push and on release, matching the pattern used in compute and other datum-cloud repos.Test plan