Travis Nielsen

@mostafaghadimi There was a problem with the rebase, see there are five commits instead of one. Please [rebase](https://rook.io/docs/rook/latest/Contributing/development-flow/#commit-history) again so there is a single commit, thanks

Are you referring to the cleanupPolicy with the `yes-really-destroy-data`? It's documented [here](https://rook.io/docs/rook/latest/Storage-Configuration/ceph-teardown/#delete-the-cephcluster-crd), so we should be already covered for this automation. Although a related thought is that the krew plugin...

It's a bit higher on the page, around this: WARNING: DATA WILL BE PERMANENTLY DELETED AFTER DELETING THE CephCluster CR WITH cleanupPolicy.

The implementation of disk cleanup is found [here](https://github.com/rook/rook/blob/master/pkg/daemon/ceph/cleanup/disk.go). It doesn't run those exact commands from the cleanup docs though.

We don't need the full list of steps from the upstream cleanup doc since the job is intended to do some very specific cleanup depending on the scenario, detect if...

IIRC we decided not to launch a cleanup job for the PVs since 1) they might not need cleanup (e.g. ebs or other cloud volumes), and 2) even if we...

Yes, that should do it.

Did you get the build to succeed yet? It does appear the core build succeeded, but a command at the end of the build failed. Error 2 usually means a...

> Obviously, two months isn't enough for fixing an issue, so please disable that lousy bot or at least give it a longer time period before chiming in. But aren't...

Did you enable the `toolbox.priorityClassName` property in [this example](https://github.com/rook/rook/blob/release-1.10/deploy/charts/rook-ceph-cluster/values.yaml#L34-L35)?