anchor.diff:  [id="overview-of-deploying-a-debezium-connector-that-uses-avro-serialization"]
   == Deployment overview
   
  -To deploy a {prodname} connector that uses Avro serialization, you must complete three main tasks: 
  +To deploy a {prodname} connector that uses Avro serialization, you must complete three main tasks:
   
   ifdef::community[]
   . Deploy an link:https://github.com/Apicurio/apicurio-registry[{registry-name-full}] instance.
   endif::community[]
   ifdef::product[]
  -. Deploy a link:{LinkServiceRegistryGetStart}[{registry-name-full} instance by following the instructions in {NameServiceRegistryGetStart}].
  +. Deploy a {registry-name-full} instance by following the instructions in link:{LinkServiceRegistryInstall}[{NameServiceRegistryInstall}].
   endif::product[]
   
   ifdef::community[]
  
positive.code:     value.converter.apicurio.registry.url: http://apicurio:8080/api
      value.converter.apicurio.registry.global-id: io.apicurio.registry.utils.serde.strategy.GetOrCreateIdStrategy
  ----
     
  .. Apply the connector instance, for example: 
  +
  `oc apply -f inventory-connector.yaml`
  +
  This registers `inventory-connector` and the connector starts to run against the `inventory` database.
  
  . Verify that the connector was created and has started to track changes in the specified database. 
  You can verify the connector instance by watching the Kafka Connect log output as, for example, `inventory-connector` starts.
  
  .. Display the Kafka Connect log output:
  
negative.code: .Procedure
  
  ifdef::community[]
  . Deploy an instance of {registry}.
  +
  The following example uses a non-production, in-memory, {registry} instance:
  +
  