1. Proposed title of this feature request

Add Option to Define Kafka Topic Prefix in Knative-Kafka Manifest 

2. What is the nature and description of the request?

Proposal to add an optional Configuration Attribute into the “Knative-Kafka” manifest.

The Idea is to be able to provide a prefix for automatic Kafka-Topic creation, when Knative uses Kafka.

Currently Kafka-Topics created by a Knative-Broker adhere to a naming convention, that use something similar to <namespace>-<broker-name>.

In a Multi-Cluster setup, where we want to share the same Kafka-Cluster this will create a problem. Why?

If both Cluster have Namespaces and Knative-Brokers deployed that have the same name, Knative runs into a conflict, as Kafka-Topics need to be unique.

The idea is, to add this additional attribute, so each Knative installation can add that prefix when it is set for automatic Kafka topic creation.

Impact:

This would change the implementation of the Knative-Kafka (serverless-operator/knative-operator/deploy/resources/knativekafka at main · openshift-knative/serverless-operator · GitHub) custom resource of OSS.

3. Why does the customer need this? (List the business requirements here)

This would solve the issue for a customer with the duplicate topic names as mentioned above. Other multicluster installations would benefit from this as well.

   
4. List any affected packages or components.

Knative