Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add separate section for Schema Registry and Kafka Connect in both config and UI #4120

Closed
2 tasks done
patrickpang opened this issue Aug 16, 2023 · 2 comments
Closed
2 tasks done
Labels
status/duplicate This issue or pull request already exists status/triage Issues pending maintainers triage type/feature A new feature

Comments

@patrickpang
Copy link

patrickpang commented Aug 16, 2023

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

Deployments of Schema Registry and Kafka Connect can be separate from Kafka clusters. For example, we can have a centralized schema registry deployment with reference to many Kafka clusters, and we can have multiple Kafka Connect clusters connecting to multiple Kafka clusters.

Currently both config and UI put Schema Registry and Kafka Connect under Kafka clusters. We would need to duplicate these configs in each cluster if we are sharing them across Kafka clusters:

kafka:
  clusters:
    - name: kafka-cluster-1
      bootstrapServers: xxx

      schemaRegistry: centralized-schema-registry
      schemaRegistryAuth:
        username: xxx
        password: xxx

      kafkaConnect:
        - name: kafka-connect-cluster-1
          address: xxx
        - name: kafka-connect-cluster-2
          address: xxx

    - name: kafka-cluster-2
      bootstrapServers: xxx

      schemaRegistry: centralized-schema-registry
      schemaRegistryAuth:
        username: xxx
        password: xxx

      kafkaConnect:
        - name: kafka-connect-cluster-1
          address: xxx
        - name: kafka-connect-cluster-2
          address: xxx

Describe the feature you're interested in

It would be good if we can have a separate section of schema registry, and kafka connect.

In config it can look like:

kafka:
  clusters:
    - name: kafka-cluster-1
      bootstrapServers: xxx
    - name: kafka-cluster-2
      bootstrapServers: xxx

  kafkaConnect:
    - name: kafka-connect-cluster-1
      address: xxx
    - name: kafka-connect-cluster-2
      address: xxx
  
  schemaRegistry: 
    - name: centralized-schema-registry
      auth:
          username: xxx
          password: xxx

In UI it can look like:

image

Describe alternatives you've considered

No response

Version you're running

56fa824

Additional context

For backwards compatibility and other use cases, we can still keep the original config, and add this as an extra.

@patrickpang patrickpang added status/triage Issues pending maintainers triage type/feature A new feature labels Aug 16, 2023
@Haarolean
Copy link
Contributor

Hi, thanks for raising the issue. Sounds like a duplicate of #1076, feel free to upvote the original issue via reactions :)

@Haarolean Haarolean closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2023
@Haarolean Haarolean added the status/duplicate This issue or pull request already exists label Aug 16, 2023
@patrickpang
Copy link
Author

@Haarolean thanks! wasn't able to search that but yeah agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/duplicate This issue or pull request already exists status/triage Issues pending maintainers triage type/feature A new feature
Projects
None yet
Development

No branches or pull requests

2 participants