chore: use ociArtifact for argo-workflows helm chart resource#93
Conversation
📝 WalkthroughWalkthroughThe pull request updates the Argo Workflows chart dependency in ChangesArgo Workflows Chart Dependency Update
Possibly related PRs
Suggested reviewers
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Switch
argo-workflows-chartfrom HTTP helm repository to OCI artifact reference.Closes #
Why
The
type: helmHTTP reference caused the chart to be embedded as alocalBlobinside the OCM component on transfer to an OCI registry, making it unaddressable as a standalone OCI artifact. This broke the standard FluxOCIRepository/HelmReleaseconsumption pattern — the chart had to be installed viaocm download resources+helm installinstead.Testing
ocm add componentversion --version 1.0.14 --create --file ./ctf component-constructor.yamllocalBlobstorage matches thefluxreference component (expected CTF behaviour)Notes for reviewers
The argoproj Helm charts are published to OCI at
ghcr.io/argoproj/argo-helm/argo-workflows. This matches the access pattern already used byarcandfluxcomponents in this repo.Checklist
Summary by CodeRabbit