Deploying Schema Registry in production in Kubernetes
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