Skip to content

[Feature] Declarative operator installation #365

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
SimonBaeumer opened this issue Aug 28, 2023 · 0 comments
Open

[Feature] Declarative operator installation #365

SimonBaeumer opened this issue Aug 28, 2023 · 0 comments

Comments

@SimonBaeumer
Copy link
Member

Problem
For cloud environments we would like to have as much control as we can about the operator installations.
We need Operators to be installed declarative, preferably via a simple image registry, pointing to an image/tag and the operator is installed without channels.

LalatenduMohanty pushed a commit to LalatenduMohanty/operator-controller that referenced this issue Dec 19, 2024
* ⚠ Status condition clean up

[RFC: ClusterCatalog Status Conditions](https://docs.google.com/document/d/1Kg8ovX8d25OqGa5utwcKbX3nN3obBl2KIYJHYz6IlKU/edit) implementation.

Closes [363](operator-framework#363)
Closes [364](operator-framework#364)
Closes [365](operator-framework#365)

Co-authored-by: Ankita Thomas <[email protected]>
Co-authored-by: Anik Bhattacharjee <[email protected]>

* Handle new finalizer code

Signed-off-by: Todd Short <[email protected]>

* Set StatusUpdated to true for finalizers

Signed-off-by: Todd Short <[email protected]>

---------

Signed-off-by: Todd Short <[email protected]>
Co-authored-by: Ankita Thomas <[email protected]>
Co-authored-by: Todd Short <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant