supertubes cluster schema-registry create 🔗︎

Create Schema Registry.

Synopsis 🔗︎

Create Schema Registry based on json/yaml stdin or file config

supertubes cluster schema-registry create [flags]

Examples 🔗︎ 


# Create Schema Registry from config file
$ supertubes cluster schema-registry create -f <path-to-schemaregistry-config-file> -n my-namespace -c <path-to-kubeconfig-file>

# Create Schema Registry from config file and wait to become active
$ supertubes cluster schema-registry create -f <path-to-schemaregistry-config-file> -n my-namespace -c <path-to-kubeconfig-file> -w

# Create Schema Registry from stdin and wait to become active
$ cat <path-to-schemaregistry-config-file> | supertubes cluster schema-registry create -n my-namespace -c <path-to-kubeconfig-file> -w

Options 🔗︎ 

  -f, --config-file string       Config file that contains the Schema Registry config.
      --create-service-account   Whether to create the service accounts specified in the SchemaRegistry descriptor. If this option is set to 'true' and there are no service accounts specified in the SchemaRegistry descriptor than a service account with <schemaregistry-name>-schema-registry will be created. (default true)
  -h, --help                     help for create
  -i, --interval int             Interval in seconds for polling Schema Registry status. (default 5)
  -k, --kafka-cluster string     Name of the Kafka cluster which this Schema Registry instance will connect to. (default "kafka")
  -n, --namespace string         Namespace that will host the Schema Registry instance. (default "kafka")
  -t, --timeout int              Timeout in seconds to wait for the Schema Registry create operation to complete. (default 150)
  -w, --wait                     Wait for Schema Registry 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 🔗︎