anchor.diff:  // ModuleID: deploying-connectors-that-use-avro-in-debezium-containers
   == Deploying with {prodname} containers
   
  -In your environment, you might want to use a provided {prodname} container to deploy {prodname} connectors that use Avro serializaion. Follow the procedure here to do that. In this procedure, you build a custom Kafka Connect container image for {prodname}, which uses the Avro converter. 
  +In your environment, you might want to use a provided {prodname} container to deploy {prodname} connectors that use Avro serializaion. Follow the procedure here to do that. In this procedure, you build a custom Kafka Connect container image for {prodname}, and you configure the {prodname} connector to use the Avro converter. 
   
   .Prerequisites
   
  -* You have the required permissions on a Kafka cluster.
  -* You downloaded the {prodname} connector plug-in that you want to deploy with Avro serialization.
  +* You have the cluster administrator access to an OpenShift cluster.
  +* You downloaded the {prodname} connector plug-in(s) that you want to deploy with Avro serialization.
   
   .Procedure
   
  +ifdef::community[]
   . Deploy an instance of {registry}. 
   +
  -ifdef::community[]
   The following example uses a non-production, in-memory, {registry}  instance:
   +
   [source,subs="attributes+"]
  
positive.code:     -p 8083:8083 debezium/connect-apicurio:{debezium-docker-label}
  ----
  endif::community[]
  ifdef::product[]
  
  .. Follow the steps in the link:{LinkCDCGettingStarted}#deploying-kafka-connect[example of deploying Kafka Connect] in {NameCDCGettingStarted}.
  .. Open the `examples/kafka-connect/kafka-connect-s2i-single-node-kafka.yaml` file that you used to deploy Kafka Connect.
  +
  Before you can create the connector instance,
  you must first enable connector resources in the `KafkaConnectS2I` Custom Resource (CR).
  
  .. In the `metadata.annotations` section, enable Kafka Connect to use connector resources.
  +
  .kafka-connect-s2i-single-node-kafka.yaml
  [source,yaml,options="nowrap"]
  ----
  apiVersion: kafka.strimzi.io/v1beta1
  kind: KafkaConnectS2I
  metadata:
    name: my-connect-cluster
    annotations:
      strimzi.io/use-connector-resources: "true"
  spec:
     ...
  ----
  
  .. Apply the updated `kafka-connect-s2i-single-node-kafka.yaml` file to update the `KafkaConnectS2I` CR:
  +
  `oc apply -f kafka-connect-s2i-single-node-kafka.yaml`
  
  .. In the Kafka Connect CR that defines the connector, add the properties that are required by the Avro converter. The CR looks like this:
  +
  .inventory-connector.yaml
  [source,yaml,options="nowrap"]
  ----
    apiVersion: kafka.strimzi.io/v1beta1
    kind: KafkaConnector
    metadata:
      name: inventory-connector  
      labels:
        strimzi.io/cluster: my-connect-cluster
    spec:
      class: io.debezium.connector.mysql.MySqlConnector
      tasksMax: 1  
      config:  
        database.hostname: mysql  
        database.port: 3306
        database.user: debezium
        database.password: dbz
        database.server.id: 184054  
        database.server.name: dbserver1  
        database.whitelist: inventory  
        database.history.kafka.bootstrap.servers: my-cluster-kafka-bootstrap:9092  
        database.history.kafka.topic: schema-changes.inventory  
        key.converter: io.apicurio.registry.utils.converter.AvroConverter
        key.converter.apicurio.registry.url: http://apicurio:8080/api
        key.converter.apicurio.registry.global-id: io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy
        value.converter: io.apicurio.registry.utils.converter.AvroConverter
        value.converter.apicurio.registry.url: http://apicurio:8080/api
        value.converter.apicurio.registry.global-id: io.apicurio.registry.utils.serde.strategy.AutoRegisterIdStrategy
  ----
     
  .. Apply the connector instance:
  +
  `$ oc apply -f inventory-connector.yaml`
  +
  This registers `inventory-connector` and the connector starts to run against the `inventory` database.
  
  .. To verify that the connector was created and has started to monitor the database, follow the steps at the end of the example procedure in link:{LinkCDCGettingStarted}#creating-connector-monitor-inventory-database[NameCDCGettingStarted].
  endif::product[]
  
  // Type: concept
  
negative.code: ----
  docker build --build-arg DEBEZIUM_VERSION={debezium-docker-label} -t debezium/connect-apicurio:{debezium-docker-label} .
  ----
  
  . Run the newly built Kafka Connect image, configuring it so it uses the Avro converter:
  +
  [source,subs="attributes+"]
  ----
  docker run -it --rm --name connect \
  