anchor.diff: -When deploying {prodname} connectors on OpenShift, it's no longer necessary to first build your own Kafka Connect image.
  -Instead, the preferred method for deploying connectors on OpenShift is to use a build configuration in {kafka-streams} to automatically build a Kafka Connect container image that includes the {prodname} connector plug-ins that you want to use.
  +With earlier versions of {kafka-streams}, to deploy {ProductName} connectors on OpenShift, you were required to first build a Kafka Connect image for the connector.
  +The current preferred method for deploying connectors on OpenShift is to use a build configuration in {kafka-streams} to automatically build a Kafka Connect container image that includes the {prodname} connector plug-ins that you want to use.
   
   During the build process, the {kafka-streams} Operator transforms input parameters in a `KafkaConnect` custom resource, including {prodname} connector definitions, into a Kafka Connect container image.
   The build downloads the necessary artifacts from the Red Hat Maven repository or another configured HTTP server.
  
positive.code: * You have access to an OpenShift cluster on which the cluster Operator is installed.
  * The {StreamsName} Operator is running.
  * An Apache Kafka cluster is deployed as documented in link:{LinkDeployStreamsOpenShift}#kafka-cluster-str[{NameDeployStreamsOpenShift}].
  * You have a {prodnamefull} license.
  * The OpenShift `oc` CLI client is installed or you have access to the OpenShift Container Platform web console.
  * Depending on how you intend to store the Kafka Connect build image, you need registry permissions or you must create an ImageStream resource:
  +
  To store the build image in an image registry, such as Red Hat Quay.io or Docker Hub::
  
negative.code: +
  [source,shell,options="nowrap"]
  ----
  oc create -n debezium -f {context}-inventory-connector.yaml
  ----
  +
  The connector is registered to the Kafka Connect cluster and starts to run against the database that is specified by `spec.config.database.dbname` in the `KafkaConnector` CR.
  