Synarcs commented on issue #31408: URL: https://github.com/apache/superset/issues/31408#issuecomment-2595031072
@villebro this makes sense, considering keeping the operator as a single monolith, with the single controller handling reconciliation for all the various combinations end-users may select to deploy superset in their environment. Some thoughts on this, maybe it would be useful in future, - We need to consider if there is a single CRD all options offered now will be converted in spec sections, specifically breaking spec section for resource into chunks to ensure each resource is configurable (following same hierarchy we keep in values for superset helm). For each section any child resources it creates would be added using proper ownerreferences, and finalizers for better gc by the superset operator. - Each of this spec subsection resembling superset architecture component can have its status as the standard way for operators to ensure the superset operator to properly reconcile and deploy each architecture component of superset. Finally, I feel, if any subsection in resource spec needs a lot much custom configuration for deployment, it would be better we break it into an isolate CRD with its own controller managed by the main superset controller to ensure the parent CRD does not become too large and difficult to manage, and the isolated component CRD in the architecture can evolve with its custom configuration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
