Camunda Self-Managed

🎬 Watch Before You Begin

c8-labs Landing Page
▶
🧭 Video Timeline

In this video, you’ll create Keycloak and Camunda secrets, generate TLS configs, install Camunda via Helm, and configure network ingress.

  • [00:05]
    Create a set of secrets associated with user accounts for Keycloak, and Camunda webapps. (Operate, Tasklist, PostgreSQL database)
  • [00:40]
    Create JKS and other configurations required for camunda install. Plus kubernetes namespace network policy.
  • [01:13]
    Install camunda app via helm script. This step takes about 5 minutes or so.
  • [01:58]
    Camunda app (representational) logs showing component list and version etc.
  • [02:30]
    See the progress via Headlamp dashboard. Pods, Deployments, Storage, Network Ingress etc.
  • [05:26]
    Create network ingress rules - Keycloak and Camunda components
  • [10:05]
    Video ends


c8-labs Landing Page
▶
🧭 Video Timeline

In this video, you’ll verify Camunda pods and webapps, check cluster topology, and deploy the Lead‑to‑Opportunity BPMN solution.

  • [00:05]
    Go through Headlamp and look at the kubernetes objects.
  • [00:45]
    Visit the Landing Page. It should be alive now.
  • [01:00]
    Visit Camunda webapps - Orchestration Admin, Operate, Tasklist etc.
  • [03:00]
    Via curl command, see the Camunda Orchestration cluster Topology.
  • [04:05]
    Deploy sample solution: Lead To Opportunity solution artifacts.
  • [04:40]
    View bpmn deployed via Operate webapp.
  • [04:52]
    Via curl command, create a new process instance.
  • [06:13]
    Video ends

Lets install Camunda components in your assigned namespace.

Add secret that holds password for various accounts.
Default Camunda user account: demo
Default Keycloak user account: admin


export UNAMESPACE={{UNAMESPACE}}


kubectl apply -f identity-secret.yaml --namespace {{UNAMESPACE}}

After this, you should see secret created in your namespace (via Project Lens UI app).
# Config => secret/identity-secret created

Used for TLS and associated configuration. Plus, a simple network policy allowing inter pod communication in the namespace.


UNAMESPACE={{UNAMESPACE}} envsubst < zeebe-makefile | sh


envsubst '${UNAMESPACE}' < c8-labs-pod-network-policy.yaml  | kubectl apply  -f -

Helm install camunda-platform


helm repo add camunda https://helm.camunda.io


helm repo update


UNAMESPACE={{UNAMESPACE}} envsubst < values-combined-ingress.yaml > values-combined-ingress.my-ns.yaml


UNAMESPACE={{UNAMESPACE}} envsubst < values-connectors-env.yaml   > values-connectors-env.my-ns.yaml


helm install {{UNAMESPACE}} camunda/camunda-platform \
  -f values-combined-ingress.my-ns.yaml \
  -f values-connectors-env.my-ns.yaml \
  --set zeebe.prometheusServiceMonitor.enabled=true \
  --version 14.4.1 --namespace {{UNAMESPACE}}

This step may take a while as it installs about a handful of pods.
You may watch the logs associated with pods to see the progress - using Project Lens or via kubectl commands.
Refer to FAQ section to see the list of kubectl commands.

Post Command-Set Execution: The output displayed on terminal window looks like this.
Click to view install logs

Post Command-Set Execution: Click to view screen shot - Camunda pods up and running.
Click on image to enlarge
Camunda Workload status
Click on image to enlarge
Camunda pods status

Add ingress to enable traffic flow to the deployed services.


envsubst '${UNAMESPACE}' < c8-ingress-keycloak.yaml  | kubectl apply  -f -


envsubst '${UNAMESPACE}' < c8-ingress.yaml           | kubectl apply  -f -


# Camunda helm install creates ingress for gRPC. 
# Run below command only if required. Check Network -> Ingress configuration for details.
# envsubst '${UNAMESPACE}' < c8-zeebe-ingress.yaml     | kubectl apply  -f -

You may check the ingress definition in the assigned namespace.

⚠️ This section completes the installation of Camunda app to your designated namespace.

Check the Pods status before validating access to the C8 environment.

Visit Landing Page:
https://{{UNAMESPACE}}.makelabs.in/

  • Keycloak Admin Console
  • C8 Orchestration Admin
  • C8 Operator
  • C8 Tasklist
  • C8 Console
  • C8 Identity
  • C8 Optimize
Note: SSO is enabled with C8 app components. You only need to sign-in to C8 once with user account demo.

Next: Deploy Lead To Opportunity sample solution