#18253·rook

Improve "authoritative" CephX key type detection

Author: BlaineEXECreated Aug 21, 2026Updated Sep 16, 2026
Labelsfeature

Is this a bug report or feature request?

  • Feature Request

What should the feature do:

Rook currently makes a best-effort attempt to determine the authoritative key types for mgr, OSD, and MDS daemons, relying on ceph auth dump-keys output.

For versions of Ceph that support this command, it would be ideal to improve this support above best-effort.

This means, Rook should be able to definitively determine the type for all possible daemons and CephX keys. If the type can't be determined (and the Ceph version supports the command), Rook should retry the reconcile until it can determine the key type to report in the associated resource status.

Important: MDS key determination should not risk examining keys belonging to other CephFilesystems. Currently, the MDS best-effort code could use keys belonging to 2+ CephFilesystems in the event one CF name is a subset of another.

Let us also report in the CephCluster status what the allowed key types are. Today, Rook supports [aes, aes256k] by default, but I do imagine this changing in the (longer term) future once kernel 7.0 becomes more widespread. Reporting Rook's internal decision on the status will help users know if they need to set allowedCiphers for their security goals.

What is use case behind this feature:

This will improve users's ability to determine compliance toward their AES256K key migration without having to rely directly on Ceph health errors/warnings.

Environment: