Lalit Maganti
c6aec79c4f
Due to #6492, preservePoolsOnDelete is not useful at all for CephFS; after the filesystem is deleted, the leftover pools cannot be reassocaited with a newly created filesystem without wiping all metadata. The only way we can actually preserve data is keeping around the entire filesystem. This commit implements a `preserveFilesystemOnDelete` option which work similar to the existing pool preservation option but instead keeps the whole CephFS while taking it down and removing all MDSes. This commit also changes all documentation to refer to this new option with the intent of essentially deprecating `preservePoolsOnDelete`. IMO, keeping around `preservePoolsOnDelete` is actively harmful because it lulls users into thinking their data will be safe but, in reality, recovering from this situation is highly complex and has large potential for data loss. Signed-off-by: Lalit Maganti <lalitm@google.com>
Build Rook's CSV file
Just run make CSV_VERSION=1.0.0 csv-ceph like this:
$ make csv-ceph CSV_VERSION=1.0.1 CSV_PLATFORM=k8s ROOK_OP_VERSION=rook/ceph:v1.0.1
INFO[0000] Generating CSV manifest version 1.0.1
INFO[0000] Fill in the following required fields in file deploy/olm-catalog/ceph.csv.yaml:
spec.keywords
spec.maintainers
spec.provider
spec.labels
INFO[0000] Create deploy/olm-catalog/ceph.csv.yaml
INFO[0000] Create deploy/olm-catalog/_generated.concat_crd.yaml
Congratulations!
Your Rook CSV 1.0.1 file for k8s is ready at: cluster/olm/ceph/deploy/olm-catalog/rook-ceph.v1.0.1.clusterserviceversion.yaml
Push it to https://github.com/operator-framework/community-operators as well as the CRDs files from cluster/olm/ceph/deploy/crds and the package file cluster/olm/ceph/assemble/rook-ceph.package.yaml.
Or for OpenShift use: $ make CSV_VERSION=1.0.0 CSV_PLATFORM=ocp csv-ceph.