...

A better solution is to store config registrations in an internal topic and perform ad hoc aggregations on registrations for a particular entity to gather compatibility information about clients that are tied to that entity. The Java producer and consumer clients can register the configs they they support and the broker can write a key-value pair to an internal topic where the key is the <user, client-id> entity and the value is ClientVersion along with the list of supported configs.  This allows compatibility information to be displayed to the user and as long as the user knows what version of client each application is using, they will know which applications will be affected by each dynamic config. For For example, all versions of clients that registered with an entity along with the supported configs for each version of client could be aggregated and returned to the user in the DescribeClientConfigsResponse. 

Public Interfaces

...

Admin Client Changes

...