mimaison commented on code in PR #24014:
URL: https://github.com/apache/kafka/pull/24014#discussion_r4483473795


##########
docs/getting-started/upgrade.md:
##########
@@ -57,6 +65,7 @@ type: docs
   * Streams groups now support the new broker configuration 
`group.streams.rack.aware.assignment.tags` and the new group configuration 
`streams.rack.aware.assignment.tags`, which set the client tag keys for 
rack-aware standby task assignment. Members missing a listed `client.tag.<key>` 
receive the new `StreamsGroupHeartbeat` status `MISSING_CLIENT_TAGS` (6), sent 
only on version 1. The built-in `sticky` assignor does not use the tags yet. 
For further details, please refer to the [Kafka Streams upgrade 
guide](/{version}/streams/upgrade-guide/).
   * Kafka Streams now supports static membership (`group.instance.id`) with 
the Streams Rebalance Protocol (`group.protocol=streams`). This requires 
brokers and clients running 4.4 or newer: brokers older than 4.4 reject 
`group.instance.id` on the streams group heartbeat with `INVALID_REQUEST`, 
which is a fatal error that shuts down the Kafka Streams client. Make sure to 
remove `group.instance.id` from all Streams applications using 
`group.protocol=streams` and restart them before downgrading brokers below 4.4. 
For further details, please refer to the [Kafka Streams upgrade 
guide](/{version}/streams/upgrade-guide/).
   * Controllers can now be unregistered from the cluster metadata. A new 
`kafka-cluster.sh unregister-controller` command and a `--unregister` flag on 
`kafka-metadata-quorum.sh remove-controller` are provided, backed by the new 
`Admin#unregisterController` API and the new `UnregisterController` RPC. This 
introduces the error code `CONTROLLER_ID_NOT_REGISTERED` (136) and requires 
metadata version `4.4-IV2` (`IBP_4_4_IV2`). For further details, please refer 
to 
[KIP-1312](https://cwiki.apache.org/confluence/spaces/KAFKA/pages/406623954/KIP-1312+Support+unregistering+controllers).
+  * ACL host patterns can now use CIDR notation, for example `192.168.0.0/24` 
or `2001:db8::/32`, in addition to a single IP address or the `*` wildcard. 
This allows a single ACL to cover a whole IPv4 or IPv6 subnet. Creating an ACL 
with a CIDR host pattern requires metadata version `4.4-IV1` (`IBP_4_4_IV1`) or 
higher; until the upgrade is finalized to that version, such requests are 
rejected with `UNSUPPORTED_VERSION`. For further details, please refer to 
KIP-1276 and [KAFKA-20088](https://issues.apache.org/jira/browse/KAFKA-20088).

Review Comment:
   Can we link to the KIP (https://cwiki.apache.org/confluence/x/DIY8G) instead 
of the JIRA?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to