Timeout waiting for node assignment about apicurio-registry-helm HOT 7 CLOSED

Try to use non SSL connection. Probably this is the issue.
And moreover, your issue should be rather addressed to developers of the apicurio-registry.

from apicurio-registry-helm.

Thank you the update. I raised ticket with apicurio registry as well.
I need to enable with SSL connection, since kafka bootstrapserver enabled with secured connection. Based on the understanding from document that apicurio will support SSL connection as well.

from apicurio-registry-helm.

Could you please just try it without SSL and report results here ?

from apicurio-registry-helm.

Yes. I disabled authorization on kafka without SSL, then i am able to deploy the apicurio registry. Please check the log file.
without-ssl-apicurio-registry.txt

from apicurio-registry-helm.

eshepelyuk - Is there any option enabled in this helm chart for TLS enabled Kafka as persistence?

from apicurio-registry-helm.

No, there is no.

from apicurio-registry-helm.

I am trying to deploy the APICURIO registry using non TLS kafka bootstrap deployed using strimzi operator on AKS. I am getting error on " org.apache.kafka.common.errors.TopicAuthorizationException: Authorization failed". In log It is crated a system topic Created new topic: kafkasql-journal then it complaining App info kafka.admin.client for adminclient-11 unregistered. In configuration there is no option to provide user .Please help me with resolution log attached.
registry.log

from apicurio-registry-helm.