[RFC #0111] - Insecure registries - Githubissues

buildpacks / rfcs

RFCs for Cloud Native Buildpacks

Apache License 2.0

57 stars 71 forks source link

[RFC #0111] - Insecure registries #246

Open natalieparellano opened 1 year ago

natalieparellano commented 1 year ago

RFC #0111 - Insecure registries

Spec:

[x] https://github.com/buildpacks/spec/issues/364
[ ] Released in platform API version TBD

Lifecycle:

[x] https://github.com/buildpacks/lifecycle/issues/524
[ ] Released in lifecycle version TBD

Pack:

[ ] https://github.com/buildpacks/pack/issues/1916
[ ] Released in pack version TBD

Documentation:

[ ] https://github.com/buildpacks/docs/issues/TBD

natalieparellano commented 1 year ago

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

wanjunlei commented 1 year ago

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

Yes

cmoulliard commented 1 year ago

What is the status of this RFC ? @natalieparellano

natalieparellano commented 1 year ago

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

dlion commented 1 year ago

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

wanjunlei commented 1 year ago

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

dlion commented 1 year ago

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

dlion commented 1 year ago

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

cmoulliard commented 1 year ago

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

dlion commented 1 year ago

Due other priorities I'm slowly working on it. It required to refactor and test imgutil (https://github.com/buildpacks/imgutil/pull/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 commented 1 year ago

Hey @natalieparellano, can you update this issue with the pack's issue I just opened? https://github.com/buildpacks/pack/issues/1916 Thanks

dlion commented 1 year ago

@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)