-
Notifications
You must be signed in to change notification settings - Fork 187
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
Helm OCI: Add support for TLS registries with self-signed certs #1097
Conversation
This is currently blocked due to kubernetes/client-go#1245 (comment). Hopefully the next controller-runtime version will fix it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@souleb please rebase and make sure you're using controller-gen v0.12. The changes to the deepcopy files should be undone.
@darkowlzz I tried to address your concerns as much as possible. |
0aa4588
to
a67929c
Compare
f1db8f0
to
2e8db08
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its looking good, found mostly nits here and there
d28bc31
to
19eecf8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! thanks @souleb 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
If implemented user will be able to provide their own custom start and bypass tls verification when interacting with OCI registries over https to pull helmCharts. Signed-off-by: Soule BA <soule@weave.works>
19eecf8
to
d45c08c
Compare
fixes #723
If implemented user will be able to provide their own custom start and bypass tls verification when interacting with OCI registries over https to pull helmCharts.