lennartjuette opened a new issue #323: URL: https://github.com/apache/solr-operator/issues/323
We are currently using Flux to roll out some of our environments on a k8s Cluster. Somewhere on this Cluster solr-operator 0.3.0 is doing it's job quite well. But there's a special scenario that I can't wrap my head around. **Scenario** We have a Kustomization (KS) that will be applied/reconciled by Flux. This KS creates a new namespace, in which other KS are placed. Those 2nd level KS install a SolrCloud instance. **Problem** When we remove one of our environments (top level KS) the namespace and all decendant KS are being purged immediately. This means that the NS is marked for termination while the SolrCloud resource is still purging it's own Resources (Pods, PVCs, ...). This seems to be a problem, because the SolrCloud won't finish cleaning up and just hang there, blocking the namespace deletion. I don't see a way to tell Flux to keep the namespace untouched until SolrCloud has been cleaned up. The only way to fix this at the moment is to remove the finalizer. Any ideas what I might be doing wrong or if something is broken here? -- 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: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
