Support for KafkaTopic CRD with standalone REST Proxy deployment #390
Description
Currently, the KafkaTopic CRD in Confluent for Kubernetes (CFK) is designed to work primarily with the REST Proxy integrated within Confluent Server, as it automatically appends /kafka to the API path when making requests to the REST Proxy endpoint.
When attempting to use the KafkaTopic CRD with a standalone REST Proxy deployment, we encounter a 404 error because the standalone REST Proxy expects requests at /v3/clusters/... instead of /kafka/v3/clusters/... which the CRD is using.
I would like to request an enhancement to the KafkaTopic CRD to support both REST Proxy implementations