Camunda 8 Self Managed installation on Premise. what is the minimum storage space required

Camunda 8 Topics
1

I am trying to install Camunda 8 self managed in on-premise. am getting below issues… Type Reason Age From Message

Normal Scheduled 70s default-scheduler Successfully assigned default/camunda-connectors-5b8fd46cd8-9jqw5 to [LINK REMOVED]
Normal Pulling 69s kubelet Pulling image “camunda/connectors-bundle:8.6.8”
Normal Pulled 60s kubelet Successfully pulled image “camunda/connectors-bundle:8.6.8” in 9.134677755s (9.134771284s including waiting)
Normal Created 60s kubelet Created container connectors
Normal Started 60s kubelet Started container connectors
Warning Evicted 51s kubelet The node was low on resource: ephemeral-storage. Threshold quantity: 1286917375, available: 719760Ki. Container connectors was using 44Ki, request is 0, has larger consumption of ephemeral-storage.
Normal Killing 51s kubelet Stopping container connectors
Warning ExceededGracePeriod 41s kubelet Container runtime did not kill the pod within specified grace period.

so what is the minimum disk space required for camunda 8 installtion. Below is the output of Kubectl get pods…

NAME READY STATUS RESTARTS AGE
camunda-connectors-5b8fd46cd8-9jqw5 0/1 Error 0 51s
camunda-connectors-5b8fd46cd8-mbnks 0/1 Pending 0 13s
camunda-elasticsearch-master-0 0/1 Running 0 51s
camunda-elasticsearch-master-1 0/1 Pending 0 51s
camunda-elasticsearch-master-2 0/1 Pending 0 7s
camunda-identity-745495bc84-5w4wc 0/1 ContainerStatusUnknown 1 51s
camunda-identity-745495bc84-mz5v2 0/1 Pending 0 34s
camunda-keycloak-0 0/1 Running 0 51s
camunda-operate-767d86c675-bpdfx 0/1 Init:0/1 0 51s
camunda-optimize-64bbd4878c-cgmgs 0/1 Init:Error 1 51s
camunda-optimize-64bbd4878c-dcvxm 0/1 Pending 0 14s
camunda-postgresql-0 1/1 Running 0 51s
camunda-tasklist-7f7975d84-pzctc 0/1 Running 0 51s
camunda-zeebe-0 0/1 Running 0 51s
camunda-zeebe-1 0/1 Pending 0 51s
camunda-zeebe-2 0/1 Running 0 51s
camunda-zeebe-gateway-df58db5c8-dhvt6 0/1 Running 0 51s
camunda-zeebe-gateway-df58db5c8-gks5q 0/1 Running 0 51s

2

Hi @sreenu_reddy1
I would start with reviewing the official documentation on this matter Sizing your environment | Camunda 8 Docs

Regards,
Alex

1 Like
3

HI @Alex_Voloshyn, in those links i can see storage required based on the instances… but i want to install first Camunda 8 with kubenates cluster… while installing on kuberntes cluster, all the pods not getting up. i am getting disk pressure issues… so to install what is the minimum memory is required.

Also we are replacing this TIBCO BPM with camunda 8 . But for TIBCO BPM its working fine with simple memory like 8GB. but in case of camunda 8 for installation itself more memory required… if yes how much storage disk memory required for this installation.

Please help.

4

Hi @sreenu_reddy1
You can set the persistence size for Camunda Platform components to a lower than default and see how it works.
In my local environment, I typically set it to Elasticsearch pods to 2Gb and it works with no issues but you need to adjust it to your real conditions.

Here is an example of how you can set it in the official Camunda Helm chart for Elasticsearch:
Take a look at the “persistence” part.

elasticsearch:
  enabled: true
  master:
    masterOnly: false
    replicaCount: 3
    heapSize: 1024m
    persistence:
      size: 2Gi
    resources:
      requests:
        cpu: 1000m
        memory: 2Gi
      limits:
        cpu: 1000m
        memory: 2Gi

Regards,
Alex

5

@Alex_Voloshyn I have updated elasticsearch pods to 1Gb… but now am getting readiness probe failed issues… what could be the reason…

NAME READY STATUS RESTARTS AGE
camunda-connectors-6b77bc9678-cgkws 0/1 Running 1 (5s ago) 3m29s
camunda-elasticsearch-master-0 0/1 Init:ErrImagePull 0 3m29s
camunda-identity-745495bc84-7gv8t 0/1 Running 1 (16s ago) 3m29s
camunda-keycloak-0 0/1 Running 1 (57s ago) 3m29s
camunda-postgresql-0 0/1 ImagePullBackOff 0 3m29s
camunda-zeebe-0 0/1 Running 0 3m9s
camunda-zeebe-1 0/1 Pending 0 3m9s
camunda-zeebe-2 0/1 Running 0 3m9s
camunda-zeebe-gateway-df58db5c8-k45r6 1/1 Running 0 3m29s
camunda-zeebe-gateway-df58db5c8-r9x5d 1/1 Running 0 3m29s

issue:

Events:
Type Reason Age From Message

Normal Scheduled 3m5s default-scheduler Successfully assigned default/camunda-connectors-6b77bc9678-cgkws to xxxxxxxx…net
Normal Pulling 3m5s kubelet Pulling image “camunda/connectors-bundle:8.6.8”
Normal Pulled 2m58s kubelet Successfully pulled image “camunda/connectors-bundle:8.6.8” in 6.635878551s (6.635887201s including waiting)
Normal Created 2m58s kubelet Created container connectors
Normal Started 2m58s kubelet Started container connectors
Warning Unhealthy 25s (x14 over 2m25s) kubelet Readiness probe failed: Get “http://1.1.1.1:8080/actuator/health/readiness”: dial tcp 1.1.1.1:8080: connect: connection refused
Warning Unhealthy 9s (x2 over 14s) kubelet Readiness probe failed: Get “http://1.1.1.1:8080/actuator/health/readiness”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

8

@sreenu_reddy1
You need to investigate the following error: