carvel-dev / carvel-dev/kapp-controller
Package Repository to tar
- Dominant language
- Go
- Stars
- 323
- Forks
- 127
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 4
Description
**Describe the problem/challenge you have**
[A description of the current challenge that you are experiencing.]
While generating Package Repository want to create the tar version of the Package Repository instead of pushing the OCI Image to a registry.
**Describe the solution you'd like**
[A clear and concise description of what you want to happen. If applicable a visual representation of the UX.]
Given that I have a folder with the Package Repository structure
When I execute
kctrl package repository release --no-push --version v1.5.1 --to-file package-repo.tar
Then my Package Repository OCI Image is created in package-repo.tar
And the OCI Image is not created in the destination Registry
**Anything else you would like to add:**
kctrl is currently using imgpkg to push the folder to a registry, which does not support the creation of tar files. We could enhance a [similar issue](https://github.com/carvel-dev/imgpkg/issues/55) in imgpkg to allow us to Push the bundle image only to the tar. The main issue with imgpkg is that imgpkg does not comply with the OCI Spec for representing the OCI Image as a tar. Due to this, we may need to use a different tool to achieve this functionality.
---
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Contributor guide
Assessment
This issue has not been assessed yet.