Camunda Self-Managed
Lets install Camunda 8.7.4 components in your assigned namespace.
Add secret that holds password for various accounts.
Default Camunda user account:
Default Keycloak user account:
# Config => secret/identity-secret created
Default Camunda user account:
demoDefault Keycloak user account:
admin
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.
UNAMESPACE=$UNAMESPACE envsubst < zeebe-makefile | sh
Helm install camunda-platform
You may watch the logs associated with pods to see the progress.
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 12.4.0 --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.
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 -
envsubst '${UNAMESPACE}' < c8-zeebe-ingress.yaml | kubectl apply -f -
You may check the ingress definition in the assigned namespace.