Travis Nielsen

I managed to get a prototype of this working... - The prototype created two Ceph clusters, each in their own K8s namespace. - Each namespace started its own Rook operator,...

This is still in progress with the investigation with #13848

Have you enabled apport? Not sure if [this thread](https://askubuntu.com/questions/1349047/where-do-i-find-core-dump-files-and-how-do-i-view-and-analyze-the-backtrace-st) is helpful, but it does indicate core dumps are not enabled by default in ubuntu stable releases.

Not that I am familiar with, I'm hoping someone else in the community may be aware

Without requiring any code changes, what if we had a script running in a daemonset (added to the examples folder) that does the following: - Mount the hostpath: `/var/lib/rook/rook-ceph/log` -...

A very simple option would also be to update the [logrotate sidecar script](https://github.com/rook/rook/blob/5a205832b88024ed25ac0e636790d58105a8d20a/pkg/operator/ceph/controller/spec.go#L126-L130) so that it periodically deletes really old files. Then we don't need any redesign or separate daemonset....

> So perhaps it would be a good thing to have the script also periodically check the fuller-scope log directory to delete files older than ~some criteria~, like 3-6 months....

Rook will apply custom labels and annotations via CRs or other Rook settings, and does not expect to preserve other customizations. Most of them are added via the cephcluster CR...

If you already have K8s infrastructure, Rook is preferred since it is designed to deploy Ceph on K8s nodes. Please do share more details to help resolve the issue you...

Looks like the issue still persists in v1.17.5, despite #16033