Repository navigation
[epic] Support direct bundle installation #597
Description
After #596 goes in, we can implement support for installing a bundle from a URL instead of resolving it from a catalog. To do this, we'll have a very strict set of guardrails:
- The bundle must be a registry+v1 bundle
- We will do minimal or no constraint/dependency checking - a direct bundle installation is considered "satisfied"
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
ncdc commentedon Jan 24, 2024
FYI @varshaprasad96
acornett21 commentedon Mar 6, 2024
With the switch happening from rukpak to kapp, it would be great if direct installs could also support Helm. The use case would be that if a helm chart exists in a helm repo, the kapp controller would be able to install it directly. The reason why this use case is important, is that it is unlikely that a helm chart maintainer would build a catalog to wrap their chart, but instead they publish it to a chart repo.
[-]Support direct bundle installation[/-][+][epic] support direct bundle installation[/+][-][epic] support direct bundle installation[/-][+][epic] Support direct bundle installation[/+]grokspawn commentedon Jul 25, 2024
A candidate brief started (but not reviewable) here
joelanford commentedon Jan 21, 2025
I implemented a proof of concept as part of #1418. We should revisit that PR when we have time to pick this issue up.
2 remaining items
github-actions commentedon Nov 12, 2025
This issue has been closed due to inactivity.
ankitathomas commentedon Apr 14, 2026
RFC: Direct Bundle Installation
We have an RFC tracking this work under review