How to Deploy Bitnami Schema Registry Helm Chart on Preinstalled Strimzi Kafka Cluster in a Separate Namespace?

Question Body: I have a Strimzi Kafka cluster already running in the kafka namespace on my GKE Kubernetes cluster. Now, I want to deploy the Bitnami Schema Registry Helm chart in a separate namespace called schema-registry.\ helm chart link: https://github.com/bitnami/charts/tree/main/bitnami/schema-registry Current Issues: Understanding ACLs required for Schema Registry’s topic access.\ Identifying the Kafka user for Schema Registry.\ Requesting a values.yaml configuration file compatible with Strimzi Kafka with mTLS authentication.(pls share values.yaml) Current Pod Error after the deployment : CMD: $ helm upgrade schema-registry oci://registry-1.docker.io/bitnamicharts/schema-registry -n schema-registry -f myvalues.yaml --install schema-registry 11:55:10.83 INFO ==> schema-registry 11:55:10.83 INFO ==> Welcome to the Bitnami schema-registry container schema-registry 11:55:10.83 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers schema-registry 11:55:10.83 INFO ==> Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami/ for more information. schema-registry 11:55:10.84 INFO ==> schema-registry 11:55:10.84 INFO ==> Starting Schema Registry setup schema-registry 11:55:10.86 INFO ==> Validating settings in SCHEMA_REGISTRY_* env vars schema-registry 11:55:10.89 INFO ==> Initializing Schema Registry schema-registry 11:55:10.90 INFO ==> Waiting for Kafka brokers to be up schema-registry 11:55:10.92 INFO ==> Schema Registry setup finished! schema-registry 11:55:10.92 INFO ==> Starting Schema Registry [2025-03-21 11:55:12,894] INFO Logging initialized @1937ms to org.eclipse.jetty.util.log.Slf4jLog (org.eclipse.jetty.util.log:170) [2025-03-21 11:55:13,088] INFO Initial capacity 128, increased by 64, maximum capacity 2147483647. (io.confluent.rest.ApplicationServer:466) [2025-03-21 11:55:13,748] INFO Adding listener: NamedURI{uri=http://0.0.0.0:8081, name='null'} (io.confluent.rest.ApplicationServer:367) [2025-03-21 11:55:13,802] INFO Registered MetricsListener to connector of listener: null (io.confluent.rest.ApplicationServer:144) [2025-03-21 11:55:14,399] INFO Found internal listener: NamedURI{uri=http://0.0.0.0:8081, name='null'} (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:201) [2025-03-21 11:55:14,401] INFO Setting my identity to version=1,host=schema-registry,port=8081,scheme=http,leaderEligibility=true,isLeader=false (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:204) [2025-03-21 11:55:16,251] INFO Registering schema provider for AVRO: io.confluent.kafka.schemaregistry.avro.AvroSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289) [2025-03-21 11:55:16,251] INFO Registering schema provider for JSON: io.confluent.kafka.schemaregistry.json.JsonSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289) [2025-03-21 11:55:16,252] INFO Registering schema provider for PROTOBUF: io.confluent.kafka.schemaregistry.protobuf.ProtobufSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289) [2025-03-21 11:55:16,393] INFO Initializing KafkaStore with broker endpoints: PLAINTEXT://versa-kafka-poc-tf-kafka-bootstrap.kafka.svc:9092 (io.confluent.kafka.schemaregistry.storage.KafkaStore:114) [2025-03-21 11:55:16,784] WARN No value specified for metadata.encoder.secret, sensitive metadata will not be encoded (io.confluent.kafka.schemaregistry.storage.encoder.MetadataEncoderService:94) [2025-03-21 11:55:16,853] INFO Creating schemas topic _schemas (io.confluent.kafka.schemaregistry.storage.KafkaStore:211) [2025-03-21 11:55:16,902] ERROR Error starting the schema registry (io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication:81) io.confluent.kafka.schemaregistry.exceptions.SchemaRegistryInitializationException: Error initializing kafka store while initializing schema registry at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:421) at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.initSchemaRegistry(SchemaRegistryRestApplication.java:79) at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.configureBaseApplication(SchemaRegistryRestApplication.java:105) at io.confluent.rest.Application.configureHandler(Application.java:323) at io.confluent.rest.ApplicationServer.doStart(ApplicationServer.java:234) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain.main(SchemaRegistryMain.java:44) Caused by: io.confluent.kafka.schemaregistry.storage.exceptions.StoreInitializationException: Failed tryin

Mar 22, 2025 - 06:21

How to Deploy Bitnami Schema Registry Helm Chart on Preinstalled Strimzi Kafka Cluster in a Separate Namespace?

Question Body:

I have a Strimzi Kafka cluster already running in the kafka namespace
on my GKE Kubernetes cluster. Now, I want to deploy the Bitnami Schema
Registry Helm chart in a separate namespace called schema-registry.\
helm chart link: https://github.com/bitnami/charts/tree/main/bitnami/schema-registry

Current Issues:

Understanding ACLs required for Schema Registry’s topic access.\
Identifying the Kafka user for Schema Registry.\
Requesting a values.yaml configuration file compatible with Strimzi Kafka with mTLS authentication.(pls share values.yaml)

Current Pod Error after the deployment :
CMD: $ helm upgrade schema-registry oci://registry-1.docker.io/bitnamicharts/schema-registry -n schema-registry -f myvalues.yaml --install

schema-registry 11:55:10.83 INFO  ==> 
schema-registry 11:55:10.83 INFO  ==> Welcome to the Bitnami schema-registry container
schema-registry 11:55:10.83 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
schema-registry 11:55:10.83 INFO  ==> Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami/ for more information.
schema-registry 11:55:10.84 INFO  ==> 
schema-registry 11:55:10.84 INFO  ==> ** Starting Schema Registry setup **
schema-registry 11:55:10.86 INFO  ==> Validating settings in SCHEMA_REGISTRY_* env vars
schema-registry 11:55:10.89 INFO  ==> Initializing Schema Registry
schema-registry 11:55:10.90 INFO  ==> Waiting for Kafka brokers to be up

schema-registry 11:55:10.92 INFO  ==> ** Schema Registry setup finished! **
schema-registry 11:55:10.92 INFO  ==> ** Starting Schema Registry **
[2025-03-21 11:55:12,894] INFO Logging initialized @1937ms to org.eclipse.jetty.util.log.Slf4jLog (org.eclipse.jetty.util.log:170)
[2025-03-21 11:55:13,088] INFO Initial capacity 128, increased by 64, maximum capacity 2147483647. (io.confluent.rest.ApplicationServer:466)
[2025-03-21 11:55:13,748] INFO Adding listener: NamedURI{uri=http://0.0.0.0:8081, name='null'} (io.confluent.rest.ApplicationServer:367)
[2025-03-21 11:55:13,802] INFO Registered MetricsListener to connector of listener: null (io.confluent.rest.ApplicationServer:144)
[2025-03-21 11:55:14,399] INFO Found internal listener: NamedURI{uri=http://0.0.0.0:8081, name='null'} (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:201)
[2025-03-21 11:55:14,401] INFO Setting my identity to version=1,host=schema-registry,port=8081,scheme=http,leaderEligibility=true,isLeader=false (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:204)
[2025-03-21 11:55:16,251] INFO Registering schema provider for AVRO: io.confluent.kafka.schemaregistry.avro.AvroSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289)
[2025-03-21 11:55:16,251] INFO Registering schema provider for JSON: io.confluent.kafka.schemaregistry.json.JsonSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289)
[2025-03-21 11:55:16,252] INFO Registering schema provider for PROTOBUF: io.confluent.kafka.schemaregistry.protobuf.ProtobufSchemaProvider (io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry:289)
[2025-03-21 11:55:16,393] INFO Initializing KafkaStore with broker endpoints: PLAINTEXT://versa-kafka-poc-tf-kafka-bootstrap.kafka.svc:9092 (io.confluent.kafka.schemaregistry.storage.KafkaStore:114)
[2025-03-21 11:55:16,784] WARN No value specified for metadata.encoder.secret, sensitive metadata will not be encoded (io.confluent.kafka.schemaregistry.storage.encoder.MetadataEncoderService:94)
[2025-03-21 11:55:16,853] INFO Creating schemas topic _schemas (io.confluent.kafka.schemaregistry.storage.KafkaStore:211)
[2025-03-21 11:55:16,902] ERROR Error starting the schema registry (io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication:81)
io.confluent.kafka.schemaregistry.exceptions.SchemaRegistryInitializationException: Error initializing kafka store while initializing schema registry
    at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:421)
    at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.initSchemaRegistry(SchemaRegistryRestApplication.java:79)
    at io.confluent.kafka.schemaregistry.rest.SchemaRegistryRestApplication.configureBaseApplication(SchemaRegistryRestApplication.java:105)
    at io.confluent.rest.Application.configureHandler(Application.java:323)
    at io.confluent.rest.ApplicationServer.doStart(ApplicationServer.java:234)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
    at io.confluent.kafka.schemaregistry.rest.SchemaRegistryMain.main(SchemaRegistryMain.java:44)
Caused by: io.confluent.kafka.schemaregistry.storage.exceptions.StoreInitializationException: Failed trying to create or validate schema topic configuration
    at io.confluent.kafka.schemaregistry.storage.KafkaStore.createOrVerifySchemaTopic(KafkaStore.java:200)
    at io.confluent.kafka.schemaregistry.storage.KafkaStore.init(KafkaStore.java:125)
    at io.confluent.kafka.schemaregistry.storage.KafkaSchemaRegistry.init(KafkaSchemaRegistry.java:419)
    ... 6 more
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed.
    at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
    at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
    at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:180)
    at io.confluent.kafka.schemaregistry.storage.KafkaStore.createSchemaTopic(KafkaStore.java:239)
    at io.confluent.kafka.schemaregistry.storage.KafkaStore.createOrVerifySchemaTopic(KafkaStore.java:192)
    ... 8 more
Caused by: org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed.