Skip to content
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

Open
2 of 7 tasks
natalieparellano opened this issue Dec 2, 2022 · 12 comments
Open
2 of 7 tasks

[RFC #0111] - Insecure registries #246

natalieparellano opened this issue Dec 2, 2022 · 12 comments

Comments

@natalieparellano
Copy link
Member

natalieparellano commented Dec 2, 2022

RFC #0111 - Insecure registries

Spec:

Lifecycle:

Pack:

Documentation:

@natalieparellano
Copy link
Member Author

@wanjunlei would you like me to assign you this issue?

@wanjunlei
Copy link
Contributor

@wanjunlei would you like me to assign you this issue?

Yes

@cmoulliard
Copy link

What is the status of this RFC ? @natalieparellano

@natalieparellano
Copy link
Member Author

@cmoulliard I believe it's just waiting to be implemented. @wanjunlei were you able to pick this up?

@dlion
Copy link
Member

dlion commented Jul 3, 2023

Hi @natalieparellano I'd like to work on this RFC if @wanjunlei didn't have the time to do so :)

@wanjunlei
Copy link
Contributor

Sorry, I don't have time to work on this feature at the moment, it would be great if you could.

@dlion
Copy link
Member

dlion commented Jul 3, 2023

Thanks @wanjunlei!
@natalieparellano can you assign it to me, please? 🙏🏼

@dlion
Copy link
Member

dlion commented Jul 4, 2023

Hey @natalieparellano , I created the issue on spec, can you update the tracking issue please?

@cmoulliard
Copy link

Do we know when this new feature supporting insecure registry will be released (lifecycle, etc) ? @natalieparellano

@dlion
Copy link
Member

dlion commented Jul 17, 2023

Due other priorities I'm slowly working on it.
It required to refactor and test imgutil (buildpacks/imgutil#211) and of course to be tested and integrated on lifecycle.
Additionally it requires to have the docs and the spec updated.

As you can see it has lots of parts that needed to be updated and tested so it will require a bit. @cmoulliard

@dlion
Copy link
Member

dlion commented Sep 21, 2023

Hey @natalieparellano, can you update this issue with the pack's issue I just opened?
buildpacks/pack#1916
Thanks

@dlion
Copy link
Member

dlion commented Sep 22, 2023

@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).
Is there other places where we need to update the doc? (if there is a way to do so)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants