support plain HTTP OCI registries in HelmRepositories #828
Conversation
This file contains 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
makkes
added
area/helm
The new field `.spec.insecure` in the HelmRepository CRD signals to the controllers that the registry is served via HTTP and not HTTPS. Signed-off-by: Max Jonas Werner <[email protected]>
|
Since helm/helm#12128 has been merged and Helm 3.13.0 released, there is actually a way to make it work |
|
this was implemented in #1288 and is included in the latest Flux release (v2.2.0) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The new field
.spec.insecurein the HelmRepository CRD signals tothe controllers that the registry is served via HTTP and not HTTPS.
closes #807
NOTE: This PR depends on a change in the Helm SDK to support configuring the registry client accordingly: helm/helm#11139