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

Might schema management be in scope? #3

Open
solsson opened this issue Dec 10, 2017 · 1 comment
Open

Might schema management be in scope? #3

solsson opened this issue Dec 10, 2017 · 1 comment

Comments

@solsson
Copy link

solsson commented Dec 10, 2017

This project is a very interesting approach to what I've been looking for in Yolean/kubernetes-kafka#101. Have you also considered managing schemas?

A topic declaration could contain Avro schema(s) and the operator could create them in Schema Registry using the -key and -value convention.

Also it seems Confluent won't support JSON schema. A REST endpoint for looking up schemas, and schema format, could be useful for those writing their own Serdes.

I started a PoC operator hack a while ago, with a CRD for topic instead of a config map. How about that?

@nbogojevic
Copy link
Owner

We currently don't use Avro schemas as we use protobuf internally, but I've heard this request already. I think it is definitely something interesting for people using them.

Personally I think the CRDs are way forward. There's some code in operator which already works with CRDs, but it has to be hardwired manually https://github.com/nbogojevic/kafka-operator/blob/master/src/main/java/nb/kafka/operator/KafkaTopicCustomResourceManager.java

One facility with ConfigMap is that you can create them from existing properties file, not sure though that it is a standard use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants