[kafka] branch 3.2 updated: MINOR: Remove kraft authorizer from list of missing features (#12146)

[ij...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ijuma pushed a commit to branch 3.2
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/3.2 by this push:
     new abcaa109e0 MINOR: Remove kraft authorizer from list of missing features (#12146)
abcaa109e0 is described below

commit abcaa109e0ae25efe3e83457dc87f7c987468656
Author: Ismael Juma <is...@juma.me.uk>
AuthorDate: Wed May 11 09:46:37 2022 -0700

    MINOR: Remove kraft authorizer from list of missing features (#12146)
    
    Also tweak the list of missing features a bit
    
    Reviewers: José Armando García Sancio <js...@users.noreply.github.com>
---
 config/kraft/README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/config/kraft/README.md b/config/kraft/README.md
index 8ba87c4844..d280f87958 100644
--- a/config/kraft/README.md
+++ b/config/kraft/README.md
@@ -114,11 +114,12 @@ We don't support any kind of upgrade right now, either to or from KRaft mode.  T
 
 Finally, the following Kafka features have not yet been fully implemented:
 
-* Support for certain security features: configuring a KRaft-based Authorizer, setting up SCRAM, delegation tokens, and so forth
-  (although note that you can use authorizers such as `kafka.security.authorizer.AclAuthorizer` with KRaft clusters, even
-  if they are ZooKeeper-based: simply define `authorizer.class.name` and configure the authorizer as you normally would).
+* Configuring SCRAM users via the administrative API
+* Supporting JBOD configurations with multiple storage directories
+* Modifying certain dynamic configurations on the standalone KRaft controller
 * Support for some configurations, like enabling unclean leader election by default or dynamically changing broker endpoints
-* Support for KIP-112 "JBOD" modes
+* Delegation tokens
+* Upgrade from ZooKeeper mode
 
 We've tried to make it clear when a feature is not supported in the preview release, but you may encounter some rough edges. We will cover these feature gaps incrementally in the `trunk` branch.