Page History

...

Sometimes there can be a need to deprecate a specific feature version (see Non-goals section). This requirement translates to increasing the cluster-wide finalized minimum version level of one or more features in the ZK '/features' node. Such feature version deprecations are typically announced in advance to the Kafka community. ThenThis is not a dynamic operation, therefore this mutation need not be supported through the Controller API. Instead, during a specific Kafka release of the Controller module, during it's the startup sequence can be made to automatically the Controller logic would be arranged to mutate the ZK '/features' node to increase the cluster-wide finalized min version level of the deprecated feature in the ZK '/features' node, to the desired new value.

Client discovery of finalized feature versions

...