villebro commented on issue #31408: URL: https://github.com/apache/superset/issues/31408#issuecomment-2573962196
> I believe this proposal is getting away from the helm finalizers as well and add custom finalizers, ownerreferences for each superset deployment-able manifest for complete lifecycle management of the state as mentioned in crd. @Synarcs I didn't mention it in the SIP, but you're right, the custom resource would be the owner of all spawned resources. In other words, when you delete the CR, it will let the k8s GC remove all child resources. Custom finalizers would be introduced as needed. However, for the first version, I think we can get by without any custom finalizers, as the GC will handle the majority of cleanup (most will probably prefer to clean up their metastore etc manually). > In addition, what are the plans for gateway networking, , I believe it would be agnostic to underlying ingress routing policy in the cluster. but will the operator also own support for deploying ingress resources for cluster running older ingress api, or resources for cluster running k8s gateway api (istio, contour, traeflik) etc. I see no reason why we can't support `Gateway` in addition to the currently supported `Ingress` resource. For this we could just add an optional `gateway` property on the CRD, making it possible to choose that one instead of `ingress` where needed. I see no reason why we can't do that as part of this SIP. To get this effort started, I think we can add it to the Helm chart first (disabled by default), and then just use a similar structure on the CRD as in the `values.yaml`. -- 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]
