Skip to main content
Version: Next

Want More?

Components in KubeVela are designed to be brought by users.

1. Get from capability center#

KubeVela allows you to explore capabilities maintained by platform team. There are two commands in kubectl vela plugin: comp and trait.

In case you haven't installed kubectl vela plugin: see this.

1. list#

For example, let's try to list all available components in a registry:

$ kubectl vela comp --discover
Showing components from registry:
cloneset default
kruise-statefulset default
openfaas default

Note that the --discover flag means show all components not in your cluster.

2. install#

Then you can install a component like:

$ kubectl vela comp get cloneset
Installing component capability cloneset
Successfully install trait: cloneset


$ kubectl get componentdefinition -n vela-system
cloneset CloneSet Describes long-running, scalable, containerized services that have a stable network endpoint to receive external network traffic from customers. It was implemented by OpenKruise Cloneset.
...(other componentDefinition)

By default, the two commands will retrieve capabilities from repo maintained by KubeVela.

2. Designed by yourself#

Check below documentations about how to bring your own components to the system in various approaches.

  • Helm - Helm chart is a natural form of component, note that you need to have a valid Helm repository (e.g. GitHub repo or a Helm hub) to host the chart in this case.
  • CUE - CUE is powerful approach to encapsulate a component and it doesn't require any repository.
  • Simple Template - Not a Helm or CUE expert? A simple template approach is also provided to define any Kubernetes API resource as a component. Note that only key-value style parameters are supported in this case.
  • Cloud Services - KubeVela allows you to declare cloud services as part of the application and provision them in consistent API.
Last updated on by kubevela-bot