Create Kafka cluster.

Synopsis 🔗︎

Create Kafka cluster based on json/yaml stdin or file cluster config. The specified cluster config must include readonly and cluster wide config also Cruise Control config.

supertubes cluster create [flags]

Examples 🔗︎


# Create Kafka cluster from cluster config file
$ supertubes cluster create -f <path-to-cluster-config-file> -n my-namespace -c <path-to-kubeconfig-file>

# Create Kafka cluster from cluster config file and wait for cluster to become active
$ supertubes cluster create -f <path-to-cluster-config-file> -n my-namespace -c <path-to-kubeconfig-file> -w

# Create Kafka cluster from cluster from stdin and wait for cluster to become active
$ cat <path-to-cluster-config-file> | supertubes cluster create -n my-namespace -c <path-to-kubeconfig-file> -w
		

Options 🔗︎

  -f, --cluster-config-file string   Config file that contains the entire Kafka cluster config including Cruise Control config to create the cluster from.
      --deploy-servicemonitor        Deploy Prometheus service monitors  for Kafka cluster and Cruise Control. This flag works only if prometheus-operator is present in the Kubernetes cluster.
  -h, --help                         help for create
  -i, --interval int                 Interval in seconds for polling Kafka cluster status. (default 5)
  -n, --namespace string             Namespace to create the KafkaCluster into. (default "kafka")
  -t, --timeout int                  Timeout in seconds to wait for the Kafka cluster create operation to complete. (default 150)
  -w, --wait                         Wait for Kafka cluster create operation to complete.

Options inherited from parent commands 🔗︎

      --accept-license                  Accept the license: https://banzaicloud.com/docs/supertubes/evaluation-license
      --color                           use colors on non-tty outputs (default true)
      --context string                  name of the kubeconfig context to use
      --formatting.force-color          force color even when non in a terminal
      --interactive                     ask questions interactively even if stdin or stdout is non-tty
  -c, --kubeconfig string               path to the kubeconfig file to use for CLI requests
      --non-interactive                 never ask questions interactively
  -o, --output string                   output format (table|yaml|json) (default "table")
      --persistent-config-file string   Supertubes persistent config file to use instead of the default at ~/.banzai/supertubes/
  -v, --verbose                         turn on debug logging

SEE ALSO 🔗︎