Deploying Schema Registry in production in Kubernetes

1/28/2020

We want to deploy Confluent Schema Registry in Kubernetes for production setup. Are there any guidelines available specifically related to Kubernetes.I followed these articles.

Schema Registry Single Datacenter Setup https://docs.confluent.io/current/schema-registry/singledc.html

High Availability for Single Primary Setup https://docs.confluent.io/current/schema-registry/index.html#sr-high-availability-single-primary

Also I am referring cp-confluent charts. I would need more info on setting right configurations in production in Kubernetes.

-- Sumit Nekar
confluent-schema-registry
kubernetes

1 Answer

1/28/2020

Schema Registry is really just a web service. There isn't much to configure outside of kafkastore.connection.url, kafkastore.topic, and optional SSL settings. Memory and disk usage is minimal, as per docs - heap size of 1GB would be more than sufficient

The Helm charts provided by Confluent work fine, and you can deploy multiple Registries fronted by an Ingress to perform load-balancing and high-availability

The high level details here apply, regardless of how you deploy it.

https://docs.confluent.io/current/schema-registry/installation/deployment.html

-- OneCricketeer
Source: StackOverflow