supertubes cluster ksqldb update 🔗︎
Update KsqlDB.
Synopsis 🔗︎
Update KsqlDB based on JSON or YAML stdin or file config
supertubes cluster ksqldb update [flags]
Examples 🔗︎
# Update KsqlDB from cluster config file
$ supertubes cluster ksqldb update -f <path-to-ksqldb-config-file> -n my-namespace --ksqldb ksql1 -c <path-to-kubeconfig-file>
# Update KsqlDB from config file and wait for the KsqlDB deployment to become active
$ supertubes cluster ksqldb update -f <path-to-ksqldb-config-file> -n my-namespace --ksqldb ksql1 -c <path-to-kubeconfig-file> -w
# Update only the KsqlDB image of the deployment and wait for the KsqlDB deployment to become active
$ supertubes cluster ksqldb update -n my-namespace --ksqldb ksqldb1 --ksqldb-image "confluentinc/cp-ksql:5.5.1" -c <path-to-kubeconfig-file> -w
# Patch KsqlDB config
$ supertubes cluster ksqldb update -n my-namespace --ksqldb ksqldb1 -c <path-to-kubeconfig-file> -w -f -<<EOF
apiVersion: kafka.banzaicloud.io/v1beta1
kind: ksqldb
spec:
  MTLS: true
EOF
		
Options 🔗︎
  -f, --config-file string    Config file that contains the KsqlDB config.
  -h, --help                  help for update
  -i, --interval int          Interval in seconds for polling KsqlDB status. (default 5)
      --ksqldb string         Name of the KsqlDB to be updated.
      --ksqldb-image string   The new image (repository/name:tag) to update KsqlDB to.
  -n, --namespace string      Namespace the KsqlDB to be updated belongs to. (default "kafka")
  -t, --timeout int           Timeout in seconds to wait for the KsqlDB update operation to complete. (default 150)
  -w, --wait                  Wait for KsqlDB update 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 🔗︎
- supertubes cluster ksqldb - Manage KsqlDB deployments
