How-to

In this section, it will introduce how to declare Helm charts as app components via ComponentDefinition.

Before reading this part, please make sure you’ve learned the definition and template concepts.

• , make sure you have installed the flux2 in the installation guide.

Here is an example ComponentDefinition about how to use Helm as schematic module.

• .spec.schematic.helm contains information of Helm release and which leverages fluxcd/flux2.
  • i.e. the pec of release aligns with and spec of repository aligns with HelmRepositorySpec.

Here is an example Application.

The component is exactly the of the Helm chart.

Deploy the application and after several minutes (it may take time to fetch Helm chart), you can check the Helm release is installed.

Check the values (image.tag = 5.1.2) from application’s properties are assigned to the chart.

KubeVela will automatically generate OpenAPI v3 JSON schema based on values.schema.json in the Helm chart, and store it in a ConfigMap in the same namespace with the definition object. Furthermore, if values.schema.json is not provided by the chart author, KubeVela will generate OpenAPI v3 JSON schema based on its values.yaml file automatically.

Please check the guide for more detail of using this schema to render GUI forms.