Closed jchunkins closed 3 years ago
I am new to this process but I would like to know how we decide if this controller lives within the catalog operator or standalone, as I mentioned above, I think consumers would get the best experience if it is packaged with OLM verses being just another operator in an OLM catalog. I think it also drives a different development cycle and process. Thoughts?
We discussed these options last Thursday at the olm-dev call:
I think folks were interested in option 2, as it allows decoupling yet reduces the packaing overhead of creating another operator, which 3rd parties would need to know to consume and enable.
/approve
This is an alternate proposal for catalog switching that uses annotations.