Kubernetes config provider in schema registry #5514
Unanswered
opsocomusr
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Did you initialized the provider? The error suggests that the value is not replaced by the client. TBH, I do not know if the Schema Registry supports the configuration providers or not. I would expect it to work in any place where Kafka client is configured. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Can we use kubernetes configuration provider in schema registry(confluent image)? The required libraries are added to the classpath and we could see the below logs when the container starts up (without using the
${secrets:namespace/secret:name}
) for the truststore and password configurations.But after changing the truststore location to
${secrets:namespace/secret:name}
in the configuration, it throws the below error.Beta Was this translation helpful? Give feedback.
All reactions