-
Notifications
You must be signed in to change notification settings - Fork 71
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
[RFC #0111] - Insecure registries #246
Comments
@wanjunlei would you like me to assign you this issue? |
Yes |
What is the status of this RFC ? @natalieparellano |
@cmoulliard I believe it's just waiting to be implemented. @wanjunlei were you able to pick this up? |
Hi @natalieparellano I'd like to work on this RFC if @wanjunlei didn't have the time to do so :) |
Sorry, I don't have time to work on this feature at the moment, it would be great if you could. |
Thanks @wanjunlei! |
Hey @natalieparellano , I created the issue on spec, can you update the tracking issue please? |
Do we know when this new feature supporting insecure registry will be released (lifecycle, etc) ? @natalieparellano |
Due other priorities I'm slowly working on it. As you can see it has lots of parts that needed to be updated and tested so it will require a bit. @cmoulliard |
Hey @natalieparellano, can you update this issue with the pack's issue I just opened? |
@natalieparellano Also I thought about the documentation issue, I think that the documentation will be automatically updated whenever we ship lifecycle, right? (I'm talking about the parameter and the description). |
RFC #0111 - Insecure registries
Spec:
TBD
Lifecycle:
TBD
Pack:
TBD
Documentation:
The text was updated successfully, but these errors were encountered: