relocate directly to target registry wihout intermediate bundle

[migmartri]

Is your feature request related to a problem? Please describe.

I am relocating a Chart and its associated container images to a target registry via the wrap/unwrap flow.

Is there any way to do the same but without requiring to pull first the images to a local tarball? the dt relocate command seems to just rewrite the references not push the container images.

Describe the solution you'd like

Relocate source -> target in one command without pulling data to an intermediate wrapped tarball.intermediate-wrapped

Describe alternatives you've considered

No response

Additional context

No response

[mpermar]

There is no such single command indeed. Yes, it would be nice to have a dt move or something like that that runs the complete flow. As you noticed, relocate only does the rewiring. I guess we haven't do it because charts-syncer works well for the team but contributions are welcomed!

Alternatively, it should be easy to have an alias that just runs the few commands together pull, relocate, push...

[migmartri]

Thanks, @mpermar, for the response.

I guess we haven't do it because charts-syncer works well for the team but contributions are welcomed!

So, does the Charts syncer perform the relocation of both the chart and container images without an intermediate wrap file?

Alternatively, it should be easy to have an alias that just runs the few commands together pull, relocate, push..

Thanks, but there are other motivations for this issue. The problem is that we run this command multiple times per day, but we do not release that often, so technically, these relocation processes should be quick no-ops.

But today, because of how wrap/unwrap seems to work (and please correct me if I am wrong), we are performing a multi-GB download + compression process to uncompress and discard it most times. This translates a bigger compute, disk, and networking footprint in our GitHub actions billing.

It feels like the tool could have a direct source-destination mode that could, from top of my head:

• 1. Download the chart
• 2. Resolve the images, either from lock file or dynamically through annotations and such as you do today.
• 3. Check if the image exists in the destination repo and push it otherwise (nitpick: if I remember correctly, it's possible to stream between two registries).
• 4. there is no need to create a tarball
• 5. Re-package the chart and push it (I believe you might not be able to know if the chart exists since, if I remember correctly, the digest changes on each helm package)

The new steps for this direct mode are 3 and 4, an optimization that should take a process that takes minutes today to seconds.

In any case, this is not a blocker for us. We might end up resolving/pushing the images ourselves and then calling relocate to rewire the chart manually. But it feels like a good addition to the already useful tool.

Thanks

[mpermar]

I don't think there is any way to instruct a registry to push into other registry. Tools like crane make it look transparent but they are pulling the bits to memory before pushing. It could be a nice feature though. No question.

Right now we don't have the capacity to do it, but PRs are more than welcome.