Skip to content

[epic] Support registry+v1 bundle installation in SingleNamespace and OwnNamespace install modes #593

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.

Sign up for GitHub

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

Jump to bottom
Open
2 of 7 tasks
ncdc opened this issue Jan 23, 2024 · 4 comments
Open
2 of 7 tasks

[epic] Support registry+v1 bundle installation in SingleNamespace and OwnNamespace install modes #593

ncdc opened this issue Jan 23, 2024 · 4 comments
Assignees
@perdasilva @thetechnick
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0

Comments

@ncdc
Copy link
Member

ncdc commented Jan 23, 2024 •
edited by perdasilva
Loading

@ncdc ncdc added the epic label Jan 23, 2024
@joelanford joelanford moved this to Todo in OLM v1 Jan 23, 2024
@ncdc ncdc changed the title Add watchNamespaces to Extension spec [epic] Support watchNamespaces Jan 23, 2024
@oceanc80 oceanc80 mentioned this issue Jan 31, 2024
Closed
4 tasks
@oceanc80
Copy link
Contributor

oceanc80 commented Jan 31, 2024 •
edited
Loading

Add ytt config

  • This should use the same method as used in OLM v0 (annotation key: 'olm.targetNamespaces')
  • Look into if watchNamespaces can be passed as parameters to ytt

@oceanc80 oceanc80 mentioned this issue Feb 1, 2024
Closed
@joelanford joelanford changed the title [epic] Support watchNamespaces [epic] Support watchNamespaces for registry+v1 bundles Mar 13, 2024
@joelanford joelanford changed the title [epic] Support watchNamespaces for registry+v1 bundles [epic] Support watchNamespaces via parameterization for registry+v1 bundles Mar 13, 2024
@joelanford joelanford mentioned this issue Mar 13, 2024
Merged
4 tasks
@joelanford joelanford added the v1.x Issues related to OLMv1 features that come after 1.0 label Apr 4, 2024
@joelanford joelanford removed the status in OLM v1 Apr 4, 2024
@joelanford joelanford changed the title [epic] Support watchNamespaces via parameterization for registry+v1 bundles [epic] Support watchNamespaces via parameterization for registry+v1 bundles in Extension API Aug 29, 2024
@LalatenduMohanty LalatenduMohanty added the triage/needs-information Indicates an issue needs more information in order to work on it. label Oct 22, 2024
@LalatenduMohanty
Copy link
Member

  • We should figure-out the use-cases we want to solve with this epic.

@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 PoC that includes parameterization related to registry+v1 watch namespaces. See #1418.

@LalatenduMohanty LalatenduMohanty mentioned this issue Feb 6, 2025
Merged
4 tasks
@LalatenduMohanty LalatenduMohanty moved this to Designing in OLM v1 Feb 11, 2025
@perdasilva perdasilva changed the title [epic] Support watchNamespaces via parameterization for registry+v1 bundles in Extension API [epic] Support registry+v1 bundle installation in SingleNamespace and OwnNamespace install modes Feb 12, 2025
@LalatenduMohanty LalatenduMohanty moved this from Designing to Implementing in OLM v1 Feb 25, 2025
@LalatenduMohanty LalatenduMohanty removed the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 18, 2025
@oceanc80
Copy link
Contributor

oceanc80 commented Apr 1, 2025

@thetechnick Do you know if the status of the remaining open issues here is correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@perdasilva perdasilva

@thetechnick thetechnick

Labels
epic v1.x Issues related to OLMv1 features that come after 1.0
Projects
OLM v1
Status: Implementing
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ncdc @joelanford @perdasilva @LalatenduMohanty @thetechnick @oceanc80