Skip to main content
Version: 8.8 (unreleased)

Helm chart custom Kubernetes manifests injection

Overview​

When using the Camunda 8 Helm chart, data can be injected into the values.yaml file, enabling the addition of extra Kubernetes manifests. This feature is particularly useful for adding custom manifests by including additional Kubernetes resources such as ConfigMaps, Deployments, or Services.

Usage​

Extra manifests are defined within your values.yaml file using the following syntax:

global:
  extraManifests:
    - |
      apiVersion: v1
      kind: ConfigMap
      metadata:
        name: example-cm-one
      data:
        test: test-one
    - |
      apiVersion: v1
      kind: ConfigMap
      metadata:
        name: example-cm-two
      data:
        test: test-two

For more information, see the Kubernetes object documentation.

Manipulate manifests​

The Camunda Helm chart is highly customizable and can be deployed in different setups. However, in some cases, you may need to adjust the rendered Kubernetes manifests directly (for example, when a feature is not supported in the chart template).

In those cases, Helm Post Rendering lets you manipulate, configure, or validate rendered manifests before Helm installs them. Post rendering is a good way to quickly add missing features to the chart. You can also raise a feature request for your use case.

Best practices​

  • Keep it simple: Use clear and concise YAML syntax to avoid complexity.
  • Use comments: Include comments in your YAML file to explain the purpose of each manifest.
  • Test thoroughly: Ensure that all added manifests are correctly formatted and functional before deployment.

Troubleshooting​

  • Syntax errors: Check for indentation issues or missing colons in key-value pairs.
  • Manifest validation: Verify that each manifest is valid and correctly formatted according to Kubernetes specifications.