[OCIRepository] Produce Helm chart artifacts #912
Closed
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.
This PR changes the behaviour of the OCIRepository controller when
.spec.layerSelector.mediaType
is set toapplication/vnd.cncf.helm.chart.content.v1.tar+gzip
, to make the resulting Flux artifact compatible with Helm.IMO OCIRepositories should produce valid Helm chart artifacts even if we chose not to use them in helm-controller. If we do chose to add
OCIRepository
as source toHelmReleases
, then this will enable chart verification (cosgin + keyless), insecure registries which are blocked upstream in Helm, and easier debugging experience (no more hidden HelmChart objects, nor HelmRepositories).Changes:
Given the following definition:
The controller produces the following result:
And the following events: