Tanzu apps workload

This topic helps you with workload life cycle management.

A workload may run as a Knative service, Kubernetes deployment, or other runtime. Workloads can be grouped together with other related resources, such as storage or credential objects as a logical application for easier management.

Workload configuration includes:

  • Source code to build
  • Runtime resource limits
  • Environment variables
  • Services to bind


  -h, --help   help for workload

Environment variables with default values

There are some environment variables that can be specify to have default values so users can execute their commands with the minimum required flags. These flags and its naming convention are listed below:

  • --type: TANZU_APPS_TYPE
  • --registry-ca-cert: TANZU_APPS_REGISTRY_CA_CERT
  • --registry-password: TANZU_APPS_REGISTRY_PASSWORD
  • --registry-username: TANZU_APPS_REGISTRY_USERNAME
  • --registry-token: TANZU_APPS_REGISTRY_TOKEN

Options inherited from parent commands

      --context name      name of the kubeconfig context to use (default is current-context defined by kubeconfig)
      --kubeconfig file   kubeconfig file (default is $HOME/.kube/config)
      --no-color          deactivate color output in terminals
  -v, --verbose int32     number for the log level verbosity (default 1)

See also

check-circle-line exclamation-circle-line close-line
Scroll to top icon