Skip to main content
Version: v1.1

How-to

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

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

Prerequisite#

Declare ComponentDefinition#

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

apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
name: webapp-chart
annotations:
definition.oam.dev/description: helm chart for webapp
spec:
workload:
definition:
apiVersion: apps/v1
kind: Deployment
schematic:
helm:
release:
chart:
spec:
chart: "podinfo"
version: "5.1.4"
repository:
url: "http://oam.dev/catalog/"

In detail:

  • .spec.workload is required to indicate the workload type of this Helm based component. Please also check for known limitations if you have multiple workloads packaged in one chart.
  • .spec.schematic.helm contains information of Helm release and repository which leverages fluxcd/flux2.

Declare an Application#

Here is an example Application.

apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: myapp
namespace: default
spec:
components:
- name: demo-podinfo
type: webapp-chart
properties:
image:
tag: "5.1.2"

The component properties is exactly the overlay values 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.

$ helm ls -A
myapp-demo-podinfo default 1 2021-03-05 02:02:18.692317102 +0000 UTC deployed podinfo-5.1.4 5.1.4

Check the workload defined in the chart has been created successfully.

$ kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
myapp-demo-podinfo 1/1 1 1 66m

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

$ kubectl get deployment myapp-demo-podinfo -o json | jq '.spec.template.spec.containers[0].image'
"ghcr.io/stefanprodan/podinfo:5.1.2"
Last updated on by yangsoon