Is anyone using Self-Encrypting Drives (SEDs) in production Ceph clusters?

I’d be interested to hear about your experience, especially any operational issues, compatibility problems, performance impact, or unexpected behavior you have encountered.

Also, if there are any Ceph-specific considerations or recommendations when using SEDs, I’d appreciate your feedback.

We did use it, but moved to ceph-volume lvm create --dmcrypt later on. I have no idea how to pair it with the orchestrator nowadays, but for us, we used it while Filestore was a thing, and we would have an unlocking step at boot, after which it was possible to start OSDs, so it wasn't very complex for us to use it, just see SED unlocking as a part of "discover which disks are OSDs on the system" which is now automated with lvm in bluestore OSDs, and the unlocking is done using the key stashed in the mons instead of a per-host local key. My guess would be that it should be possible for the newly unlocked SED drives to present the lvm identifier that triggers ceph-osd@ systemd unit to kick into effect and start the OSD, but I haven't been using SED since ceph jewel so.. -- May the most significant bit of your life be positive.