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