anchor.diff:  .Procedure
   
   . Create a new `KafkaConnect` custom resource using the same name as the name used for the `KafkaconnectS2I` resource.
  -. Copy the `KafkaconnectS2I` resource properties to the `KafkaConnect` resource.
  +. Copy the `KafkaConnectS2I` resource properties to the `KafkaConnect` resource.
   . If specified, make sure you use the same `spec.config` properties:
   +
   --
  
positive.code: 
  [role="_abstract"]
  Support for Kafka Connect with S2I and the `KafkaConnectS2I` resource is planned for deprecation.
  The decision follows the introduction of `build` configuration properties to the `KafkaConnect` resource,
  which are used to build a container image with the connector plugins you require for your data connections automatically.
  
  This procedure describes how to migrate your Kafka Connect with S2I instance to a standard Kafka Connect instance.
  To do this, you configure a new `KafkaConnect` custom resource to replace the `KafkaConnectS2I` resource, which is deleted.
  
  WARNING: The migration process involves downtime from the moment `KafkaConnectS2I` instance is deleted until the new `KafkaConnect` instance has been successfully deployed.
  During this time, connectors will not be running and processing data. However, after the changeover they should continue from the point at which they stopped.
  
  .Prerequisites
  
negative.code: +
  [source,shell,subs="+quotes"]
  ----
  kubectl get kctr --selector strimzi.io/cluster=_MY-KAFKA-CONNECT-CLUSTER_ -o name
  ----
  +
  Replace _MY-KAFKA-CONNECT-CLUSTER_ with the name of your Kafka Connect cluster.
  