kubevela.github.io/docs/cli/vela_addon_enable.md

title
vela addon enable

enable an addon

Synopsis

enable an addon in cluster.

vela addon enable [flags]

Examples

  Enable addon by:
	vela addon enable <addon-name>
  Enable addon with specify version:
	vela addon enable <addon-name> --version <addon-version>
  Enable addon for specific clusters, (local means control plane):
	vela addon enable <addon-name> --clusters={local,cluster1,cluster2}
  Enable addon locally:
	vela addon enable <your-local-addon-path>
  Enable addon with specified args (the args should be defined in addon's parameters):
	vela addon enable <addon-name> <my-parameter-of-addon>=<my-value>
  Enable addon with specified registry:
    vela addon enable <registryName>/<addonName>

Options

  -c, --clusters string           specify the runtime-clusters to enable
      --dry-run                   render all yaml files out without real execute it
  -h, --help                      help for enable
      --override-definitions      override existing definitions if conflict with those contained in this addon
  -s, --skip-version-validating   skip validating system version requirement
  -v, --version string            specify the addon version to enable
  -y, --yes                       all checks will be skipped and the default answer is yes for all validation check.

Options inherited from parent commands

  -V, --verbosity Level   number for the log level verbosity

SEE ALSO

• vela addon - Manage addons for extension.

Go Back to CLI Commands Homepage.

Auto generated by spf13/cobra script in KubeVela.