-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for insecure registries in HelmRepositories of Type oci #807
Comments
Could you please implement this for both OCI and regular (non-OCI) HTTP repositories? Thanks in advance |
I just noticed that the EKS-A folks are maintaining a Helm fork with some patches: aws/eks-anywhere#2536 There's also a bunch of upstream Helm issues and PRs around this so I'll try to find a way for Helm to settle on a quick way forward. |
Submitted this MR to Helm to get the options needed for this. |
Helm will support plain HTTP registries in its next release due to the merging of helm/helm#12128 |
Looks like t has been merged now, 3.13.0 has been released. I was wondering if this means that this issue/feature can now progress? Thanks! |
|
Please don't comment on closed issues but create a new one and provide more details (Flux version, HelmRepository spec etc.). |
The idea is to provide the ability to declare a registry as
insecure
and to be able to communicate with thehttp
scheme.The text was updated successfully, but these errors were encountered: