What?

Replace our custom midstream quota plugin with an updated version of the Strimzi quota plugin.

Why?

With kafka 3.3 we gain access to KIP-827 which means we have all the required information about storage volumes available via the Admin API to make quota decisions. This allows us to build a version of the quota plug-in which can be used upstream and stops maintaining a separate fork.

How?

Working upstream in the Strimzi community design (via a proposal) & build a new version using KIP-827. There is an upstream issue to seed the upstream effort.
Given strimzi supports multiple versions of kafka the new version of the plug-in needs to be able to support both API versions in parallel.
There might be a desire for a Srimzi proposal to cover the effort, depending on how significant the changes to the quota plug-in need to be.

The new version of the quota plug-in would need kafka 3.3 to be deployed before we can remove our custom version. However the upstream work does not depend on that as kafka 3.3.x is already a supported version in Strimzi.