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

Enhance docs to explain differences between fetch from image vs. fetch from imgpkgBundle #713

Open
asaikali opened this issue Oct 22, 2023 · 3 comments
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@asaikali
Copy link

The docs on App CR High Level Overview shows all the places where configurations can be fetched from. Enhance the docs to explain what is the differences similarities between fetching from fetch from an image vs. fetch from imgpkgBundle

If the overview section is the wrong place to add this info, then maybe consider adding a page on fetching strategies with a discussion of the pros/cons of each approach to fetching.

@asaikali asaikali added carvel-triage enhancement This issue is a feature request labels Oct 22, 2023
@100mik
Copy link
Contributor

100mik commented Oct 22, 2023

It would be great to call out how Carvel tooling enables relocatable bundles while leveraging imgpkg with the Packaging APIs.

Especially calling out bits like how dependent images are relocated. And even how bundle references are recursed into. I am going to leave this for triage as this issue might not belong to this repository.
This is definitely something we want to take note of in our documentation more explicitly.

Copy link

github-actions bot commented Dec 2, 2023

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

@github-actions github-actions bot added the stale This issue has had no activity for a while and will be closed soon label Dec 2, 2023
@praveenrewar praveenrewar added discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution and removed stale This issue has had no activity for a while and will be closed soon labels Dec 5, 2023
@renuy renuy added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution carvel-triage labels Jan 9, 2024
@renuy renuy transferred this issue from carvel-dev/kapp-controller Jan 9, 2024
@renuy
Copy link
Contributor

renuy commented Jan 9, 2024

Moving to carvel repo for doc enhancements

@renuy renuy added the carvel accepted This issue should be considered for future work and that the triage process has been completed label Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

4 participants