Set the following examples in provisioning.yaml
Simple configuration, with JMX metrics
The URLs (nodes) should always have a scheme defined (http:// or https://).
Copy confluentSchemaRegistry :
- name : schema-registry
tags : [ "tag1" ]
version : 1
configuration :
schemaRegistryUrls :
value :
- http://my-sr.host1:8081
- http://my-sr.host2:8081
## all metrics properties are optional
metricsPort :
value : 9581
metricsType :
value : JMX
metricsSsl :
value : false
Basic authentication
For Basic Authentication, define username
and password
properties.
Copy confluentSchemaRegistry :
- name : schema-registry
tags : [ "tag1" ]
version : 1
configuration :
schemaRegistryUrls :
value :
- http://my-sr.host1:8081
- http://my-sr.host2:8081
username :
value : my-username
password :
value : my-password
TLS with custom truststore
A custom truststore is needed when the Schema Registry is served over TLS (encryption-in-transit) and the Registry’s certificate is not signed by a trusted CA.
Copy confluentSchemaRegistry :
- name : schema-registry
tags : [ "tag1" ]
version : 1
configuration :
schemaRegistryUrls :
value :
- http://my-sr.host1:8081
- http://my-sr.host2:8081
sslTruststore :
fileRef :
filePath : /path/to/my/truststore.jks
sslTruststorePassword :
value : myPassword
TLS with client authentication
A custom truststore might be necessary too (see above).
Copy confluentSchemaRegistry :
- name : schema-registry
tags : [ "tag1" ]
version : 1
configuration :
schemaRegistryUrls :
value :
- http://my-sr.host1:8081
- http://my-sr.host2:8081
sslKeystore :
fileRef :
filePath : /path/to/my/keystore.jks
sslKeystorePassword :
value : myPassword
Hard or soft delete
By default, Lenses will use hard delete for Schema Registry. To use soft delete, add the following property:
Copy confluentSchemaRegistry :
- name : schema-registry
tags : [ "tag1" ]
version : 1
configuration :
schemaRegistryUrls :
value :
- http://my-sr.host1:8081
- http://my-sr.host2:8081
hardDelete :
value : true