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

[epic] Support watchNamespaces via parameterization for registry+v1 bundles in Extension API #593

Open
3 tasks
ncdc opened this issue Jan 23, 2024 · 2 comments
Labels
epic triage/needs-information Indicates an issue needs more information in order to work on it. v1.x Issues related to OLMv1 features that come after 1.0 v1.1

Comments

@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
Copy link
Contributor

oceanc80 commented Jan 31, 2024

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

@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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic triage/needs-information Indicates an issue needs more information in order to work on it. v1.x Issues related to OLMv1 features that come after 1.0 v1.1
Projects
Status: No status
Development

No branches or pull requests

4 participants