...

Currently, Apache Kafka lacks a mechanism to enforce configuration constraints that are tied to specific metadata.versionlevels. As Kafka’s metadata evolves, certain configuration values that were considered valid in older versions may become semantically incorrect or unsafe in newer ones. Without a validation layer to enforce these version-specific constraints, two primary issues arise:

...

Compatibility, Deprecation, and Migration Plan

• Add  unit test and integration test to cover new feature.
• When admin upgrade or downgrade to specific metadata version, if there is any illegal config, it will return InvalidConfigError.

Test Plan

...

• Add  unit test and integration test to cover new feature.

Rejected Alternatives

If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.