This quick start shows you how to use Confluent Operator to get up and running with Confluent Platform and its main components.
Step 3. Deploy Confluent Operator
The operator-util.sh
script deploys and starts Confluent Operator and Confluent Platform.
Important
Do not use operator-util.sh
for production environments. The script is
designed for quick installs and testing.
To deploy all components, enter the following command from in the scripts
directory where you downloaded the Operator bundle.
./operator-util.sh -n <namespace> -r <release-prefix> -f $VALUES_FILE
The following options are used in the command:
- -n or –namespace: If you do not enter a new namespace, the namespace used is the default Kubernetes namespace. Typically, you should enter a new simple namespace.
operator
is used in the example below.
- -r or –release: A release prefix to use. This creates a unique release name for each component.
co1
is used in the example below.
- -f or –helm-file: The path to the provider YAML file. The
$VALUES_FILE
environment variable is used in this tutorial.
The following shows an example using namespace operator
and prefix co1
.
./operator-util.sh -n operator -r co1 -f $VALUES_FILE
It takes a few minutes for the script to completely deploy all components. You may see messages like the following when the script is running. This is normal and typically occurs because Apache Kafka® pods take a while to start up.
Error from server (NotFound): statefulsets.apps "ksql" not found
Retry 1/10 exited 1, retrying in 1 seconds...
Error from server (NotFound): statefulsets.apps "ksql" not found
Retry 2/10 exited 1, retrying in 2 seconds...
Error from server (NotFound): statefulsets.apps "ksql" not found
Retry 3/10 exited 1, retrying in 4 seconds...
NAME DESIRED CURRENT AGE
ksql 2 2 4s
Run Command:
kubectl --context gke-platform-develop -n operator rollout status sts/ksql -w
When the script completes, enter the following command:
kubectl get pods -n operator
The following output should be displayed.
NAME READY STATUS RESTARTS AGE
cc-operator-76c54d65cd-vgm5w 1/1 Running 0 7m28s
connectors-0 1/1 Running 0 2m17s
connectors-1 1/1 Running 0 2m17s
controlcenter-0 1/1 Running 0 2m14s
kafka-0 1/1 Running 0 6m23s
kafka-1 1/1 Running 0 4m58s
kafka-2 1/1 Running 0 3m40s
ksql-0 1/1 Running 0 2m10s
ksql-1 1/1 Running 0 2m10s
replicator-0 1/1 Running 0 2m7s
replicator-1 1/1 Running 0 2m7s
schemaregistry-0 1/1 Running 0 2m4s
schemaregistry-1 1/1 Running 0 2m4s
zookeeper-0 1/1 Running 0 7m15s
zookeeper-1 1/1 Running 0 7m15s
zookeeper-2 1/1 Running 0 7m15s
Tip
If you want to delete components, enter the command ./operator-util.sh --delete -n <namespace> -r <release> -f $VALUES_FILE
.