<p>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.</p>

<p>Schema Registry Single Datacenter Setup
<a href="https://docs.confluent.io/current/schema-registry/singledc.html" rel="nofollow noreferrer">https://docs.confluent.io/current/schema-registry/singledc.html</a></p>

<p>High Availability for Single Primary Setup
<a href="https://docs.confluent.io/current/schema-registry/index.html#sr-high-availability-single-primary" rel="nofollow noreferrer">https://docs.confluent.io/current/schema-registry/index.html#sr-high-availability-single-primary</a></p>

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

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

<p>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</p>

<p>The high level details here apply, regardless of how you deploy it. </p>

<p><a href="https://docs.confluent.io/current/schema-registry/installation/deployment.html" rel="nofollow noreferrer">https://docs.confluent.io/current/schema-registry/installation/deployment.html</a></p>
