KPD closed beta Sign inRequest access

3. Set up dev, test and prod

Describe the three clusters and the two Flink compute pools, and put the pipeline on production.

Part 3 of 10 in the Hello World tutorial · Follow this part in the guided wizard · Printable version

A normal setup has three environments: dev to build and try things, test to check a release, and prod for real use. You created a cluster for each in Part 1; now you describe them, look at the compute pools, and say which cluster the pipeline runs on.

KPD never needs your credentialsClusters hold names, types, regions and ids, never keys or passwords. Terraform gets every secret from variables your CI supplies.

Describe each cluster

  1. In the explorer, open Environments → Clusters. The three clusters are listed with their type.
Environments → Clusters in the explorer.
Environments → Clusters in the explorer.
  1. Click hwc-prod. The Edit cluster dialog opens.
  2. Look at the fields: Bootstrap server, Environment ID (env-…) and Cluster ID (lkc-…) come from Confluent Cloud once the cluster exists. Leave them empty for this tutorial: KPD reminds you about them (as information, not errors) and Terraform marks them as TODOs.
  3. Description: type Production: where the store-orders pipeline runs. Ids to add once the cluster exists. and click Save.
Edit cluster. The ids are what Terraform needs to find a real cluster; leave them empty for now.
Edit cluster. The ids are what Terraform needs to find a real cluster; leave them empty for now.
  1. Do the same for hwc-dev (Development: for building and trying things out. Ids to add once the cluster exists.) and hwc-test (Test: for testing a release before production.).
More clusters laterRight-click Clusters and choose New Kafka cluster… to add one at any time.
Right-click Clusters → New Kafka cluster…
Right-click Clusters → New Kafka cluster…

Check the compute pools

Flink statements run in a compute pool, measured in CFUs (Confluent Flink Units). Each statement needs at least one, so a 10 CFU pool holds up to ten statements. Using one pool per stage keeps a busy stage from starving the other.

  1. Under Stream configuration → Flink compute pools, click hwc-raw-to-cdm.
  2. Check Max CFUs is 10. Leave Existing pool ID empty (fill it only if the pool already exists, and Terraform will use it instead of creating one).
  3. Description: Process stage: the statement that joins raw orders and customers into the canonical order. Click Save.
  4. Click hwc-cdm-to-surface and give it the description Surface stage: the two data product statements.
Edit compute pool: name, cloud, region, max CFUs and a description.
Edit compute pool: name, cloud, region, max CFUs and a description.

Put the pipeline on production

  1. Click an empty part of the canvas so the pipeline's settings show.
  2. Kafka cluster: choose hwc-prod (prod). The cluster's name now appears large in the corner of the canvas, so you always know where a pipeline runs.
The pipeline runs on hwc-prod. That is why every topic name in this tutorial starts hwc.prod.
The pipeline runs on hwc-prod. That is why every topic name in this tutorial starts hwc.prod.

Save. Next: 4. Build the pipeline.