Skip to content

Latest commit

 

History

History
 
 

operator

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

Confluent Operator with Confluent Cloud

Objective

Quickly test Confluent Operator with Confluent Cloud and Minikube.

It starts:

  • Connect
  • Control Center
  • KSQL

IMPORTANT: it requires tweaks to helm templates file, see tweaks here

It also showcases a connector example (SpoolDir) and Prometheus/Grafana example.

Prerequisites

All you have to do is to be already logged in with confluent CLI.

By default, a new Confluent Cloud environment with a Cluster will be created.

You can configure the cluster by setting environment variables:

  • CLUSTER_CLOUD: The Cloud provider (possible values: aws, gcp and azure, default aws)
  • CLUSTER_REGION: The Cloud region (use confluent kafka region list to get the list, default eu-west-2)
  • CLUSTER_TYPE: The type of cluster (possible values: basic, standard and dedicated, default basic)
  • ENVIRONMENT (optional): The environment id where want your new cluster (example: env-xxxxx)

In case you want to use your own existing cluster, you need to setup these environment variables:

  • ENVIRONMENT: The environment id where your cluster is located (example: env-xxxxx)
  • CLUSTER_NAME: The cluster name
  • CLUSTER_CLOUD: The Cloud provider (possible values: aws, gcp and azure)
  • CLUSTER_REGION: The Cloud region (example us-east-2)
  • CLUSTER_CREDS: The Kafka api key and secret to use, it should be separated with semi-colon (example: <API_KEY>:<API_KEY_SECRET>)
  • SCHEMA_REGISTRY_CREDS (optional, if not set, new one will be created): The Schema Registry api key and secret to use, it should be separated with semi-colon (example: <SR_API_KEY>:<SR_API_KEY_SECRET>)

How to run

Simply run:

$ playground run -f start<tab>