Ramkumar Chinchani
Ramkumar Chinchani
> what is the issue you are trying to fix? We have a situation where our registry is behind a proxy which enforces Content-Length maximums. Since dist-spec allows this chunked...
> If a proxy imposes a limit on Content-Length, I can’t see how that could be possibly reasonably discoverable by a registry client; In the general case, yes it is...
Would it be possible instead try to delete by tag first and if that fails, fallback to digest?
At least on the registry side [1], we have modeled this as a configurable policy [2] so that clients are free to issue any API call they want, but the...
Aye. As a data point, this is how zot does it ... as a dist-spec extension, https://github.com/project-zot/zot/blob/main/pkg/extensions/_zot.md https://github.com/project-zot/zot/blob/main/pkg/extensions/search/search.md
cc: @rareddy
@dhirajsb This proposal is aligned with https://github.com/kubeflow/community/pull/682/files#diff-aaf54745ecb36016135c83a5a41a03025574ecb492aec56ef6d2c7c902abfe17R180 Basically, why invent a new piece of machinery when a required infra piece like the container registry is evolving to be more general-purpose....
Cross-posting here ... https://kccnceu2024.sched.com/event/1YeLi ^ This idea is spreading around I suppose ... https://github.com/kubecon EU 2024
Will try to give a presentation on next Kubeflow registry meeting on Apr 1. Best to give a demo on current dist-spec v1.1.0 capabilities and then field follow-up questions.
@vanhtuan0409 is this a CDN use case? Also, what would zot actually need to do here?