[Q] Build OCI image to tarball and push it by external tool

[bademux]

Hi,

It would be nice to use already existing push-with-crane job in CI.

Is it possible to build helm OCI artifact to tarball? Would be it possible to push artifact as generic OCI image.

Thanks for the great tool!

[gjenkins8]

Is it possible to build helm OCI artifact to tarball?

certainly - https://helm.sh/docs/helm/helm_package/

I would like to think helm push would be more convenient, etc. Is there a specific reason to not prefer helm push?

[gjenkins8]

Thanks for the great tool!

thanks!

[bademux]

Is it possible to build helm OCI artifact to tarball?

certainly - https://helm.sh/docs/helm/helm_package/

I would like to think helm push would be more convenient, etc. Is there a specific reason to not prefer helm push?

Yes, for highly isolated environments Push action are handled by special jobs on CI.
For docker it would go like that:

1. Build image as tar in first stage (Google Jib\Kaniko)
2. Push tar by another one (crane\docker load push)

Another minor reason is convenient listing end artifact without access to remote repo.

I I understand correctly the result of helm package can be pushed with external tool?

[sabre1041]

@bademux if you do so, and want to pull/retrieve it via Helm, you will need to populate a compatible OCI artifact. I can share the specific details as I did produce this previously work ORAS some time ago.

[bademux]

@sabre1041 looks like I mess with problem description; sorry and let me try again:
I want to use helm for creating local tgz and installing local folder\tgz in cluster,
but for communication: pushing\puling I want to use 3rd party tool.

[sabre1041]

@sabre1041 looks like I mess with problem description; sorry and let me try again: I want to use helm for creating local tgz and installing local folder\tgz in cluster, but for communication: pushing\puling I want to use 3rd party tool.

helm package will enable to packaging and then you are free to use the tool of choice for transport

[bademux]

@sabre1041 thanks.

• from what I understand to push image to OCI registry I will need manifest.json
• how to pull helm chart from OCI with 3rdparty tooling

[sabre1041]

@bademux Use a tool like ORAS to manage OCI artifacts

[bademux]

@sabre1041
thanks, I will try that one (looks like that demo can be helpful)

But I wonder if something like docker image save \ docker image load can be implemented. Instead of actual HTTP operation on registry just tarball is saved\loaded from disk.

[sabre1041]

@bademux ORAS and Helm use OCI Artifacts instead of OCI images, so using docker image * would not be applicable

[bademux]

thanks you for guiding me, lets apply my new knowledge!