younsl commented on issue #434: URL: https://github.com/apache/superset-kubernetes-operator/issues/434#issuecomment-6167271435
Thanks for the ping @villebro. A few requests from the GitOps side (Argo CD + ESO), mostly following patterns this [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) already has: - Separate `SupersetDatabase` and `SupersetDataset` kinds, in line with the dedicated-CR direction from #314, so Argo CD can order them with sync waves - Database credentials only via `passwordFrom`, resolved by the kubelet in the import Job, so the operator still never reads Secret values ([Secret Handling](https://apache.github.io/superset-kubernetes-operator/reference/security/#secret-handling)) - A `deletionPolicy` field like the existing Job retention policy, defaulting to `Retain`, since deleting a dataset breaks dependent charts and an Argo CD prune shouldn't cause that - An `Available` condition with `observedGeneration`, and wait until the referenced `Superset` is Available before importing <details> <summary>Architecture sketch</summary> <img width="2408" height="1328" alt="Proposed SupersetDatabase and SupersetDataset architecture" src="https://github.com/user-attachments/assets/a2d43b8e-f30c-460c-bbf3-3d82dfb8c204"; /> </details> These are suggestions based on common operator and GitOps practices, not a settled design, and the field names in the sketch are illustrative. Suggest starting with databases and datasets only. Happy to review the design. -- 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]
