Skip to content
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

Pull and push package commands #2557

Open
bgrant0607 opened this issue Oct 16, 2021 · 4 comments
Open

Pull and push package commands #2557

bgrant0607 opened this issue Oct 16, 2021 · 4 comments
Labels
area/pkg enhancement New feature or request p2 triaged Issue has been triaged by adding an `area/` label

Comments

@bgrant0607
Copy link
Contributor

Once kpt supports multiple storage types, it would be useful to abstract it more.

Pkg get changes upstream info. I just want to get the bits without using git or other storage command. Read-only use cases like GitOps could use this.

Push is harder, but even more useful because the git mechanics are pretty complicated, and OCI will be different. We will need to prototype a couple options for deciding on the recommended approach.

Cc @justinsb

@bgrant0607 bgrant0607 added the enhancement New feature or request label Oct 16, 2021
@droot droot added area/pkg triaged Issue has been triaged by adding an `area/` label labels Oct 20, 2021
@droot
Copy link
Contributor

droot commented Oct 20, 2021

push seems to have an overlap with kpt pkg publish command we have thought about in the past.

Pkg get changes upstream info. I just want to get the bits without using git or other storage command.

Can you tell more about the use-cases here (especially not updating the bits in the kpt metadata) ? In the git-ops case, if one wants ignore kptfile, then having storage metadata doesn't hurt much.

@bgrant0607
Copy link
Contributor Author

I don't want to ignore the Kptfile. I want to preserve the Kptfile as is.

The GitOps use case is basically: while true ; do kpt pkg pull package/version && kpt live apply ; done

My other use cases are for changing the package itself:

  • Pull and then kpt pkg upgrade | kpt fn render, push
  • Pull and then kpt fn source | mutate | kpt fn sink | kpt fn render, push

@bgrant0607
Copy link
Contributor Author

imgpkg has an interesting push/pull model.
https://github.com/vmware-tanzu/carvel-imgpkg
https://carvel.dev/imgpkg/

@bgrant0607
Copy link
Contributor Author

Interestingly, adding support for more storage backends, including OCI, is what motivated helm to add push:
https://github.com/helm/community/blob/main/hips/hip-0006.md

@droot droot added the p2 label May 27, 2022
@mortent mortent added this to kpt Jan 21, 2023
@mortent mortent moved this to Backlog in kpt Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/pkg enhancement New feature or request p2 triaged Issue has been triaged by adding an `area/` label
Projects
None yet
Development

No branches or pull requests

2 participants