render-helm-chart: Kustomize Inline Values #

Overview #

This example demonstrates how to declaratively invoke the render-helm-chart function with kustomize using the valuesInline field.

Function invocation #

To use the function with kustomize, you can specify the functionConfig in your kustomization’s generators field. This example uses inline values to use instead of the default values accompanying the chart:

kustomization.yaml:

generators:
- |-
  apiVersion: fn.kpt.dev/v1alpha1
  kind: RenderHelmChart
  metadata:
    name: demo
    annotations:
      config.kubernetes.io/function: |
        container:
          network: true
          image: ghcr.io/kptdev/krm-functions-catalog/render-helm-chart:latest
  helmCharts:
  - name: ocp-pipeline
    namespace: mynamespace
    version: 0.1.16
    repo: https://bcgov.github.io/helm-charts
    releaseName: moria
    valuesInline:
      releaseNamespace: ""
      rbac:
        create: true
        rules:
          - apiGroups: [""]
            verbs: ["*"]
            resources: ["*"]

Then, to build the kustomization with kustomize v4:

kustomize build --enable-alpha-plugins --network .

Expected result #

You should also be able to find the line def releaseNamespace = "" somewhere in your output, as well as the following:

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: moria-ocp-pipeline
  namespace: mynamespace
rules:
- apiGroups:
  - ""
  resources:
  - '*'
  verbs:
  - '*'
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: moria-ocp-pipeline
  namespace: mynamespace
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: moria-ocp-pipeline
subjects:
- kind: ServiceAccount
  name: jenkins
  namespace: mynamespace

which demonstrates that the correct values provided via valuesInline were used.