-
Notifications
You must be signed in to change notification settings - Fork 584
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
Unable to specify CA for Helm OCI repository #3417
Comments
This is blocked upstream. We are working with the helm maintainer to fix it. In the meantime, what you can do is patch the |
any updates on this? Trying to migrate my local instances to use OCI in Harbor but having the same issue as mentioned here. |
As mentioned:
See helm/helm#11711 |
This will be resolved by fluxcd/source-controller#723 |
A satisfaying workaround is to mount CA in source controller using method 3 of this tip
|
Great you found that. Paulo also suggested this in #2921 (comment). I suppose we should add it as an item to the FAQ page. |
fixed in fluxcd/source-controller#1097 |
Describe the bug
At the moment, there is no possibility of using a custom certificate authority against a HelmRepository of type
oci
. While authentication makes sense to implement later down the line, the ability of trusting a CA should be something that is needed.Steps to reproduce
secretRef
withcaFile
setExpected behavior
I expect that it will accept it since I provided a CA file.
Screenshots and recordings
N/A
OS / Distro
N/A
Flux version
v0.37.0
Flux check
root@ctl1:~# flux check
► checking prerequisites
✔ Kubernetes 1.22.17 >=1.20.6-0
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.27.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.31.0
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.29.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.32.1
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta1
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta1
✔ receivers.notification.toolkit.fluxcd.io/v1beta1
✔ all checks passed
Git provider
N/A
Container Registry provider
Distribution (formerly Docker Registry)
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: