DBZ-4582 Clarify that an existing KC can be used to deploy a connector
This commit is contained in:
parent
f9f00164d1
commit
0168cfb1e9
@ -25,7 +25,7 @@ ImageStreams are not available by default.
|
||||
.Procedure
|
||||
|
||||
. Log in to the OpenShift cluster.
|
||||
. Create a new {prodname} `KafkaConnect` custom resource (CR) for the connector.
|
||||
. Create a {prodname} `KafkaConnect` custom resource (CR) for the connector, or modify an existing one.
|
||||
For example, create a `KafkaConnect` CR that specifies the `metadata.annotations` and `spec.build` properties, as shown in the following example.
|
||||
Save the file with a name such as `dbz-connect.yaml`.
|
||||
+
|
||||
|
Loading…
Reference in New Issue
Block a user