Skip to content

[epic] Support direct bundle installation #597

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

Open
ncdc opened this issue Jan 24, 2024 · 5 comments
Open

[epic] Support direct bundle installation #597

ncdc opened this issue Jan 24, 2024 · 5 comments
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0

Comments

@ncdc
Copy link
Member

ncdc commented Jan 24, 2024

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:

  1. The bundle must be a registry+v1 bundle
  2. We will do minimal or no constraint/dependency checking - a direct bundle installation is considered "satisfied"
@ncdc ncdc added the epic label Jan 24, 2024
@ncdc
Copy link
Member Author

ncdc commented Jan 24, 2024

FYI @varshaprasad96

@acornett21
Copy link
Contributor

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.

@joelanford joelanford moved this to Needs Design in OLM v1 Mar 7, 2024
@joelanford joelanford added the v1.x Issues related to OLMv1 features that come after 1.0 label Apr 4, 2024
@joelanford joelanford changed the title Support direct bundle installation [epic] support direct bundle installation Apr 4, 2024
@joelanford joelanford changed the title [epic] support direct bundle installation [epic] Support direct bundle installation Apr 4, 2024
@joelanford joelanford removed the status in OLM v1 Apr 4, 2024
@grokspawn
Copy link
Contributor

A candidate brief started (but not reviewable) here

@LalatenduMohanty LalatenduMohanty added v1.1 and removed v1.x Issues related to OLMv1 features that come after 1.0 labels Nov 5, 2024
@LalatenduMohanty LalatenduMohanty added the v1.x Issues related to OLMv1 features that come after 1.0 label Dec 10, 2024
@joelanford
Copy link
Member

I implemented a proof of concept as part of #1418. We should revisit that PR when we have time to pick this issue up.

@grokspawn
Copy link
Contributor

This requires us to determine a way to feature-gate API changes before we could work it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

5 participants