-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal : Building tarred bundles without being dependent on a OCI registry #737
Conversation
✅ Deploy Preview for carvel canceled.
|
…egistry Signed-off-by: ashpect <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the Proposal looks good, the only thing that I would add to it is a paragraph to enfasize that imgpkg push --to-oci-tar will only create in disk the OCI image for the bundle itself. In the future we can have the inflate flag that might help with that use case.
I also added some answers for the open questions.
After we add this I think the proposal is ready to be approved.
I am sorry for the delay to get this proposal through.
Signed-off-by: ashpect <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As soon as we have no more open questions I think we can change the document to Review state, send the link again to the Carvel Slack channel, wait for any other review, or the consensus period expires, and we can Approve and merge the proposal.
proposals/repo-to-tar/README.md
Outdated
--- | ||
title: "Building tarred bundles without being dependent on a OCI registry" | ||
authors: [ "Ashish Kumar <[email protected]>" ] | ||
status: "draft" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
status: "draft" | |
status: "review" |
Signed-off-by: ashpect <[email protected]>
Signed-off-by: ashpect <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: ashpect <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A step in the direction for resolving the issue 1277.
For discussion, see PR 692