0.3.0
or above is required.
Consult the Operator documentation to get started with the Operator.
The examples in the guide will assume you’ve deployed on a kind
cluster using our recommended kind
config, but can be adjusted to suit your environment.
BigPeer
custom resource.
For example:
bp1
.
BigPeerApp
resource.
For example:
example-app
on the bp1
Big Peer. The appId
is used to identify the App across different Big Peers and will be needed when configuring CDC.
baseDomain
if you need to make the Kafka topics available over a specific domain you have an ingress for.
For this guide, we’ll assume you’ve deployed using the recommended kind
cluster deployment, and we’ll establish a path on localhost by setting baseDomain
to kafka.localhost
:
kafka-connectors
.
Wait a few minutes for all the pods to be ready:
ditto-connectors
Helm chart.
First, create a Helm values file with the configuration needed to deploy CDC:
cdc
, cdc-heartbeat
and stream-splitter
pods running:
kafka-connectors-cluster-ca-cert
. Otherwise, it will take the name of the release used for the Kafka installation, suffixed by -cluster-ca-cert
.
From this secret, extract and base64 decode the PKCS#12 certificate and password for use with your Kafka client.
2164bef3-37c0-489c-9ac6-c94b034525d7-all-true
topic.
Identify your endpoint hostname
kafka-connectors-kafka-connectors-0
.From here, you can obtain the hostname with:ditto-broker-0.kafka.localhost
.Run the console consumer
kind
cluster and hosting the ingress on kafka.localhost
, you may experience some DNS errors here.This is due to how the Java runtime, which the console consumer is built upon, resolves DNS.Adding an entry to your system’s /etc/hosts
should address this issue, for example:
echo "127.0.0.1 ditto-broker-0.kafka.localhost:443" >> /etc/hosts
Verify changes are streaming
helm
delete on the Helm release made during installation: