When the cruise control integration was originally written, then was no formal definition of the Cruise Control REST API. As a result we wrote our own client interface which we used for the main implementation and mocking for testing.

Cruise Control now has a formal OpenAPI specification. We should use this to:

• Replace the client interface with one generated from the OpenAPI spec (via tools such as the openapi-generator).
• The generation should be part of the build (by using tools such as openapi-generator-maven-plugin) so that if we update the version we are pulling the relevant spec version.
• Reimplement the Strimzi CC client on top of the generated client classes.
• Use MockServer's OpenAPI support to ensure we are generating accurate test endpoints for the given version of Cruise Control. This will be a marked improvement compared to the current situation where we need to manually align the endpoints, parameters and responses.