...

As of the date of writing, several the following features have not yet been implemented in KRaft mode.

• Supporting JBOD configurations with multiple storage directories

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-14127

• Modifying certain dynamic configurations on the standalone KRaft controller

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-14349

• Delegation tokens

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-15219

As outlined aboveWhile the lack of these features in the current KRaft codebase is frustrating, we expect to close these gaps over the course of the next few monthssoon.

Compatibility, Deprecation, and Migration Plan

...

One possible objection is that we should not declare KRaft to be production ready until it has reached full feature parity with ZooKeeper mode. My response to this is that we expect to close the feature gaps relatively quickly – especially upgrade, which should be fully taken care of in 3.4. There is still a lot of value in marking KRaft as production ready now. In addition to enabling more usage, it will ensure that we do not end up with more feature gaps to fill over the next few months.

...