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

Activity

1. ncdc

   added

   epic

   on Jan 23, 2024
2. joelanford

   added this to OLM v1on Jan 23, 2024
3. joelanford

   moved this to Todo in OLM v1on Jan 23, 2024
4. ncdc

   changed the title [-]Add watchNamespaces to Extension spec[/-] [+][epic] Support watchNamespaces[/+] on Jan 23, 2024
5. oceanc80 commented on Jan 31, 2024

   

   oceanc80

   on Jan 31, 2024

   Last edited by oceanc80

   Contributor

   More actions

   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
6. joelanford

   changed the title [-][epic] Support watchNamespaces[/-] [+][epic] Support watchNamespaces for registry+v1 bundles[/+] on Mar 13, 2024
7. joelanford

   changed the title [-][epic] Support watchNamespaces for registry+v1 bundles[/-] [+][epic] Support watchNamespaces via parameterization for registry+v1 bundles[/+] on Mar 13, 2024
8. joelanford

   added

   v1.xIssues related to OLMv1 features that come after 1.0Issues related to OLMv1 features that come after 1.0

   on Apr 4, 2024
9. joelanford

   moved this from Accepted to No status in OLM v1on Apr 4, 2024
10. 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[/+] on Aug 29, 2024
11. LalatenduMohanty

    added

    triage/needs-informationIndicates an issue needs more information in order to work on it.Indicates an issue needs more information in order to work on it.

    on Oct 22, 2024
12. LalatenduMohanty commented on Oct 22, 2024

    

    LalatenduMohanty

    on Oct 22, 2024

    Member

    More actions

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

    added

    v1.1

    and removed

    v1.xIssues related to OLMv1 features that come after 1.0Issues related to OLMv1 features that come after 1.0

    on Nov 5, 2024
14. LalatenduMohanty

    added

    v1.xIssues related to OLMv1 features that come after 1.0Issues related to OLMv1 features that come after 1.0

    on Dec 10, 2024
15. 6 remaining items

    Load more
16. LalatenduMohanty

    moved this from Designing to Implementing in OLM v1on Feb 25, 2025
17. LalatenduMohanty

    removed

    triage/needs-informationIndicates an issue needs more information in order to work on it.Indicates an issue needs more information in order to work on it.

    on Mar 18, 2025
18. oceanc80 commented on Apr 1, 2025

    

    oceanc80

    on Apr 1, 2025

    Contributor

    More actions

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

    added sub-issues on Apr 1, 2025

    • [epic] Add capability to run feature gated e2e tests #1890
    • Create e2e tests for registry+v1 bundle installation in SingleNamespace and OwnNamespace install modes #1891
20. oceanc80

    removed sub-issues on Apr 1, 2025

    • [epic] Add capability to run feature gated e2e tests #1890
    • Create e2e tests for registry+v1 bundle installation in SingleNamespace and OwnNamespace install modes #1891
21. ankitathomas

    moved this from Implementing to Needs Docs in OLM v1on May 27, 2025
22. github-actions commented on Oct 14, 2025

    

    github-actionsbot

    on Oct 14, 2025 – with GitHub Actions

    More actions

    Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
23. github-actions

    added

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.

    on Oct 14, 2025
24. github-actions

    removed

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.

    on Nov 7, 2025
25. github-actions commented on Mar 2, 2026

    

    github-actionsbot

    on Mar 2, 2026 – with GitHub Actions

    More actions

    Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
26. github-actions

    added

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.

    on Mar 2, 2026
27. github-actions commented on Apr 1, 2026

    

    github-actionsbot

    on Apr 1, 2026 – with GitHub Actions

    More actions

    This issue has been closed due to inactivity.
28. github-actions

    closed this as not plannedon Apr 1, 2026