Internal topics prefix and name configurable

[Perdjesk]

Is your feature request related to a problem? Please describe. Given a multi-tenant Kafka cluster with ACLs per tenant based on prefixes, running ksqldb server should not require new ACLs.

Example: TenantA ACLs: PREFIXED tenant-a. TenantB ACLs: PREFIXED tenant-b.

Each tenant should be able to run KSQLDB on their existing respective topics without new ACLs.

Describe the solution you'd like Make the KSQLDB server internal topics fully configurable, include prefix, name and suffix.

The following value should be configurable by KsqlConfig defaulting to existing hard-coded values. https://github.com/confluentinc/ksql/blob/53ffec880fed46a31d4d67de26c8c5028c20602c/ksqldb-common/src/main/java/io/confluent/ksql/util/ReservedInternalTopics.java#L30-L34

The delimiter used between the service id and suffix should be configurable as well. https://github.com/confluentinc/ksql/blob/53ffec880fed46a31d4d67de26c8c5028c20602c/ksqldb-common/src/main/java/io/confluent/ksql/util/ReservedInternalTopics.java#L93-L95

Describe alternatives you've considered Adding new ACLs per tenant containing the hard-coded prefix _confluent-ksql- and enforcing tenant to use a prefix for their KSQL service id. TenantA ACLs: PREFIXED _confluent-ksql-tenant-a. TenantB ACLs: PREFIXED _confluent-ksql-tenant-b.

Additional context Similar to https://github.com/confluentinc/ksql/issues/2933

[yashpandey8055]

Any movements on this ? Because we can't configure internal topics for our managed kafka in organization

[ocadaruma]

@yashpandey8055 Proposed new KLIP regarding this. https://github.com/confluentinc/ksql/pull/9170

[ikus060]

Any progress on this subject. Our Kafka has specific requirement to have our topic name start with <tenant_name>-

So we would like to replace the value "_confluent-ksql" by something else...

[rkravinder05]

Any updates on this?

[suhas-satish]

Not currently planned on the roadmap

[usmanovbf]

still actual