my-rook-config

Files

T

Sébastien Han 05775b068d osd: handle removal of encrypted osd deployment

This is handling a tricky scenario where the OSD deployment is manually
removed and the OSD never reconvers. This is unlikely to happen, but
still OSD should be able to run after that action. Essentially after a
manual deletion, we need to run the prepare job again to re-hydrate the
OSD information so that the OSD deployment can be deployed.
On encryption, it is a little bit tricky since ceph-volume list again
the main block won't return anything, so we need to target the encrypted
block to list.
There is another case this PR does not handle, which is the removal of
the OSD deployment and then the node is restarted. This means that the
encrypted container is not opened anymore. However, opening it requires
more work like writing the key on the filesystem (if not coming from the
Kubernete secret, eg,. KMS vault) and then run luksOpen. This is an
extreme corner case probably not worth worrying about for now.

Signed-off-by: Sébastien Han <seb@redhat.com>

2021-12-21 10:51:09 +01:00

device_test.go

ceph: disable raw mode for disks

2021-07-22 09:59:56 -06:00

device.go

osd: handle removal of encrypted osd deployment

2021-12-21 10:51:09 +01:00

kmod.go

exec: always write commands to debug log

2020-03-19 07:49:54 -06:00

log.go

Migrate logging package from built-in to github.com/coreos/capnslog, allow user specified logging level, tune logging levels for existing log statements