Hello there,
I want to deploy a self-managed Zeebe Cluster using Kubernetes KIND, but I’m struggling because the zeebe repository zeebe/zeebe-full-helm is now deprecated.
I know that there is an other repo of the zeebe releases, but I’m lost into it when the Docs say please refer to the Installation Guide for details.
Therefore: Does anybody know how to add the new zeebe releases to helm? Maybe with zbctl deploy?
Hello @KameraUndA ,
Zeebe is part of Camunda Platform 8. There is a dedicated section for installing Camunda Platform 8 using a helm chart. It also contains a reference towards a values file especially for kind:
I hope this helps
Jonathan
It is deprecated over more than a year now. You can read about it here as well camunda-platform-helm | Camunda Platform 8 Self-Managed Helm charts
We have also written a migration guide that might help you History for MIGRATION.md - camunda/camunda-platform-helm · GitHub
Greets
Chris
Sorry, I guess I forgot to answer…
Thanks a lot! I already knew that, but through that and @Zelldon s reply I saw for the first time, that helm repo add camunda https://helm.camunda.io helm repo update no longer refers to full-helm. That was my sticking point.
Anyway, now I come to the CAMUNDA PLATFORM writing, but the zeebe-self-managed-tasklist-… and -operate have CrashLoopBackOffs and then errors. I’ll see what the problem is.
Another problem was that I can’t install the yaml named in the tutorial, but as I saw in the Docs, there is something newer: --values https://raw.githubusercontent.com/camunda/camunda-platform-helm/main/charts/camunda-platform/values/values-latest.yaml
for the install zeebe-self-managed camunda/camunda-platform step
However, I still habe the CrashLoopBackOff errors 
And I’m little bit lost to find the soultion. Does anybody have a way? (Maybe @nathan.loding ?)
Here is my kubectl get pods -w answer from the last try (reinstalling)
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Terminating 0 3m43s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Running 0 2m12s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 Pending 0 2m12s
zeebe-self-managed-keycloak-0 0/1 PodInitializing 0 47s
zeebe-self-managed-operate-67487d6dcc-5tpmk 0/1 Running 0 2m12s
zeebe-self-managed-optimize-54ff79856-sffjx 0/1 Running 0 2m12s
zeebe-self-managed-postgresql-0 0/1 Terminating 0 3m44s
zeebe-self-managed-tasklist-86d7bf955-brbnp 0/1 ContainerCreating 0 2m12s
zeebe-self-managed-zeebe-0 0/1 Terminating 0 3m43s
zeebe-self-managed-zeebe-gateway-59bc669899-4ncsm 0/1 Pending 0 2m12s
zeebe-self-managed-zeebe-gateway-59bc669899-64qgg 0/1 Pending 0 2m12s
zeebe-self-managed-zeebe-gateway-59bc669899-v2fzq 0/1 Terminating 0 3m44s
zeebe-self-managed-tasklist-86d7bf955-brbnp 0/1 Running 0 2m13s
zeebe-self-managed-zeebe-gateway-59bc669899-v2fzq 0/1 Terminating 0 4m27s
zeebe-self-managed-zeebe-gateway-59bc669899-v2fzq 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-gateway-59bc669899-v2fzq 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-gateway-59bc669899-v2fzq 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-gateway-59bc669899-64qgg 0/1 Pending 0 2m56s
zeebe-self-managed-zeebe-0 0/1 Terminating 0 4m27s
zeebe-self-managed-zeebe-gateway-59bc669899-64qgg 0/1 ContainerCreating 0 2m56s
zeebe-self-managed-zeebe-0 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-0 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-0 0/1 Terminating 0 4m28s
zeebe-self-managed-zeebe-gateway-59bc669899-64qgg 0/1 Running 0 2m58s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 Pending 0 3m6s
zeebe-self-managed-zeebe-gateway-59bc669899-4ncsm 0/1 Pending 0 3m6s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 ContainerCreating 0 3m6s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 Running 0 3m9s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Error 0 3m10s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Running 1 (3s ago) 3m11s
zeebe-self-managed-postgresql-0 0/1 Terminating 0 5m4s
zeebe-self-managed-postgresql-0 1/1 Terminating 0 5m14s
zeebe-self-managed-postgresql-0 0/1 Terminating 0 5m37s
zeebe-self-managed-postgresql-0 0/1 Terminating 0 5m37s
zeebe-self-managed-postgresql-0 0/1 Terminating 0 5m37s
zeebe-self-managed-operate-67487d6dcc-5tpmk 0/1 Error 0 4m36s
zeebe-self-managed-operate-67487d6dcc-5tpmk 0/1 Running 1 (4s ago) 4m37s
elasticsearch-master-0 0/1 Terminating 0 6m11s
elasticsearch-master-0 0/1 Terminating 0 6m13s
elasticsearch-master-0 0/1 Terminating 0 6m13s
elasticsearch-master-0 0/1 Terminating 0 6m13s
elasticsearch-master-0 0/1 Pending 0 0s
elasticsearch-master-1 0/1 Pending 0 0s
elasticsearch-master-0 0/1 Pending 0 0s
elasticsearch-master-1 0/1 Pending 0 0s
elasticsearch-master-0 0/1 Init:0/1 0 0s
zeebe-self-managed-zeebe-0 0/1 Pending 0 0s
zeebe-self-managed-postgresql-0 0/1 Pending 0 0s
zeebe-self-managed-zeebe-1 0/1 Pending 0 0s
zeebe-self-managed-zeebe-2 0/1 Pending 0 0s
zeebe-self-managed-zeebe-0 0/1 Pending 0 0s
zeebe-self-managed-postgresql-0 0/1 Pending 0 0s
zeebe-self-managed-zeebe-1 0/1 Pending 0 0s
zeebe-self-managed-postgresql-0 0/1 ContainerCreating 0 0s
zeebe-self-managed-zeebe-2 0/1 Pending 0 0s
elasticsearch-master-0 0/1 Init:0/1 0 5s
zeebe-self-managed-postgresql-0 0/1 Running 0 5s
elasticsearch-master-0 0/1 PodInitializing 0 6s
elasticsearch-master-0 0/1 Running 0 8s
zeebe-self-managed-postgresql-0 1/1 Running 0 21s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Error 1 (2m48s ago) 5m56s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 CrashLoopBackOff 1 (14s ago) 6m9s
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Running 2 (16s ago) 6m11s
zeebe-self-managed-tasklist-86d7bf955-brbnp 0/1 Error 0 6m35s
zeebe-self-managed-tasklist-86d7bf955-brbnp 0/1 Running 1 (4s ago) 6m37s
zeebe-self-managed-keycloak-0 0/1 Running 0 5m13s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 Error 0 6m44s
zeebe-self-managed-identity-85bcb4476c-msbtz 0/1 Running 1 (3s ago) 6m46s
zeebe-self-managed-keycloak-0 1/1 Running 0 7m21s
zeebe-self-managed-operate-67487d6dcc-5tpmk 0/1 Error 1 (4m27s ago) 9m
zeebe-self-managed-connectors-69c575bd5c-4jlmq 0/1 Error 2 (3m11s ago) 9m6s
To me it looks like you have several helm releases installed in your current namespace. Is this the case?
helm list and check the output.helm uninstall
Alternatively and probably the fast way would be to delete the current namespace and create a new one, than all resources bound to the namespace are deleted as well.
Greets
Chris
Thank you and @jonathan.lukas, I hadn’t noticed that.
However, after several attempts, even when refreshing the cluster (including checking if everything is empty in Docker Desktop) when reinstalling, I unfortunately still get CrashLoopBackOffs
Here the version where I installed my Helm chart with the --values :
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Running 0 17m
elasticsearch-master-1 0/1 Pending 0 17m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 Running 5 (3m16s ago) 17m
zeebe-self-managed-identity-569fc6577d-p5lvp 0/1 Pending 0 17m
zeebe-self-managed-keycloak-0 1/1 Running 0 17m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 Running 4 (117s ago) 17m
zeebe-self-managed-optimize-57bf6685b9-tl6gx 0/1 Running 0 17m
zeebe-self-managed-postgresql-0 1/1 Running 0 17m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 Error 3 (4m14s ago) 17m
zeebe-self-managed-zeebe-0 0/1 Running 0 17m
zeebe-self-managed-zeebe-1 0/1 Pending 0 17m
zeebe-self-managed-zeebe-2 0/1 Pending 0 17m
zeebe-self-managed-zeebe-gateway-5dc85bc798-ldlts 0/1 Running 0 17m
zeebe-self-managed-zeebe-gateway-5dc85bc798-zsdnx 0/1 Pending 0 17m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 CrashLoopBackOff 3 (12s ago) 17m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 Error 5 (3m38s ago) 17m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 Running 4 (41s ago) 17m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 CrashLoopBackOff 5 (14s ago) 17m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 Error 4 (4m17s ago) 19m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 CrashLoopBackOff 4 (12s ago) 19m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 Running 6 (2m42s ago) 20m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 Running 5 (90s ago) 21m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 Error 4 (4m15s ago) 21m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 CrashLoopBackOff 4 (15s ago) 21m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 Error 6 (4m44s ago) 22m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 CrashLoopBackOff 6 (16s ago) 22m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 Running 5 (85s ago) 22m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 Error 5 (5m1s ago) 24m
zeebe-self-managed-operate-75695c55d6-47mzr 0/1 CrashLoopBackOff 5 (16s ago) 24m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 Error 5 (5m6s ago) 26m
zeebe-self-managed-tasklist-54b54f6b6-8v6bs 0/1 CrashLoopBackOff 5 (11s ago) 26m
zeebe-self-managed-connectors-5d96b7f58b-nnk72 0/1 Running 7 (5m5s ago) 27m
At the end I used kubectl delete pvc --all to delete all pvcs.
Ok I took another name “zaaba” & “zaaba-sm” on another try. Here the connecors and the identity are ready:
elasticsearch-master-0 0/1 Pending 0 12m
elasticsearch-master-1 0/1 Pending 0 12m
zaaba-sm-connectors-76cb47f568-7jkpv 1/1 Running 1 (9m30s ago) 12m
zaaba-sm-identity-68f9b6d5c6-r4czr 1/1 Running 0 12m
zaaba-sm-keycloak-0 1/1 Running 0 12m
zaaba-sm-operate-9c69bdb5d-7p26j 0/1 Running 2 (2m57s ago) 12m
zaaba-sm-optimize-7ddfbc45c-l487k 0/1 Running 0 12m
zaaba-sm-postgresql-0 1/1 Running 0 12m
zaaba-sm-tasklist-8475c75ddb-89572 0/1 Running 2 (3m47s ago) 12m
zaaba-sm-zeebe-0 0/1 Running 0 12m
zaaba-sm-zeebe-1 0/1 Pending 0 12m
zaaba-sm-zeebe-2 0/1 Pending 0 12m
zaaba-sm-zeebe-gateway-7c7656f956-4zfxn 0/1 Running 0 12m
zaaba-sm-zeebe-gateway-7c7656f956-78wtc 0/1 Pending 0 12m
Hmm and wait, we only have the free version. It says “Non-Production usage of Operate, Tasklist, Optimize”. Is that why it simply doesn’t work at this point?
Hi @KameraUndA,
No, the images for production and non-production usage are all the same.
Hope this helps, Ingo