Travis Nielsen fbf3837f13 ceph: stop removing osds for any cephcluster CR update ...

Removing an OSD unintentionally can result in data loss,
which is to be prevented at all costs. Rook's functionality
to remove OSDs automatically when a node was removed from the
cluster CR has led on several occasions to users having OSDs
unintentionally removed from their cluster.

If the admin decides they really need to remove OSDs they should
do it as a one-time action that they intentionally run
rather than the operator attempting to manage the deletion
with desired state. The risk of misinterpreting the desired
state, even with a typo, is too great.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>

2019-12-13 08:26:23 -07:00

..

cassandra

crds: Set annotations pods, deployments and so on

2019-04-16 20:47:05 +02:00

ceph

ceph: stop removing osds for any cephcluster CR update

2019-12-13 08:26:23 -07:00

cockroachdb

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00

discover

rook: add owner reference to discover cm

2019-12-12 15:10:06 +01:00

edgefs

edgefs: payloads on an S3 service

2019-12-06 19:16:43 +02:00

k8sutil

k8sutil: cmdreporter: properly set app name

2019-11-14 15:50:26 -07:00

minio

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00

nfs

nfs: revert nfs operator pid location

2019-12-09 14:31:03 -07:00

test

Ceph: Add unit tests for nfs-ganesha spec

2019-07-22 11:06:04 -06:00

yugabytedb

ownerrefs: set owners based on name instead of namespace

2019-10-14 09:29:45 -06:00