HI [~dffrench],
Also, I'd like to highlight that it is the design proposed for the operator-framework and would not be a good practice at all keep a box with many things mixed there. How much atomic are the objects/types and implementations better are to keep them maintained.
IMHO, it very intuitive that each kind should have its own controller and etc .. however, we also can check this info gave him for an operator-framework teammate. See https://github.com/operator-framework/operator-sdk/issues/1383
Regards your comment
bq. the operator should automatically create the DB CR without the user explicitly creating it themselves.
[~dffrench] how to initialize an object that was not declared/defined? Note that the CRD is like an object/class and the operator is already creating it automatically when the same is applied in the namespace. Is it make sense? Should we keep this task or could we close it? If you would like to keep it, could you please describe what exactly should be done here?
|
|
