Elasticsearch pod problem during helm install

Camunda 8 Topics
1

I’m trying to deploy Camunda on local machine by fallowing Guide ‘Local Kubernetes Cluster’
After helm install command elasticsearch-master-0 pod is in status ‘Running’ but Ready is ‘0/1’

When I execute ‘kubectl describe pods elasticsearch-master-0’ I’m getting below error

Warning Unhealthy 2m4s (x51 over 9m34s) kubelet (combined from similar events): Readiness probe errored: rpc error: code = Unknown desc = failed to exec in container: failed to start exec “a8e6d89a1e6fb001580cb0373cd35f9982cfcb723493ba5b30a9a5de69393550”: OCI runtime exec failed: exec failed: unable to start container process: error adding pid 6151 to cgroups: failed to write 6151: openat2 /sys/fs/cgroup/unified/kubelet.slice/kubelet-kubepods.slice/kubelet-kubepods-burstable.slice/kubelet-kubepods-burstable-pod68dd10f1_1027_46d1_92eb_3004afec9580.slice/cri-containerd-f13ea217d5f417e64c7cf432170b00fbbcbe2aca4168e5624f8c0655171d3b31.scope/cgroup.procs: no such file or directory: unknown

I’m using kind with podman and below helm values file override

global:
  identity:
    auth:
      # Disable the Identity authentication for local development
      # it will fall back to basic-auth: demo/demo as default user
      enabled: false

# Disable identity as part of the camunda platform core
identity:
  enabled: false

optimize:
  enabled: false

# Reduce for Zeebe and Gateway the configured replicas and with that the required resources
# to get it running locally
zeebe:
  clusterSize: 1
  partitionCount: 1
  replicationFactor: 1
  pvcSize: 10Gi

zeebe-gateway:
  replicas: 1

connectors:
  enabled: true
  inbound:
    mode: disabled

# Configure elastic search to make it running for local development
elasticsearch:
  replicas: 1
  # Allow no backup for single node setups
  clusterHealthCheckParams: "wait_for_status=yellow&timeout=1s"

  # Request smaller persistent volumes.
  volumeClaimTemplate:
    accessModes: [ "ReadWriteOnce" ]
    storageClassName: "standard"
    resources:
      requests:
        storage: 15Gi

Can someone help me with this problem?
Thanks in advance!

2

Hi @zoran4 - that’s an interesting error, one I haven’t encountered working with kind and that configuration locally. Have you tried doing an uninstall (helm uninstall camunda-platform) and removing any local PVCs (kubectl pvc delete command), then reinstalling?

3

I’m running into the same issues running podman. Were you able to solve this issue?

4

Hi, no I installed it on the end by using docker images

1 Like
5

Thanks for letting me know!

I now ended up doing the same, used Podmans docker compose compatibility extension and just upped the docker-compose.yaml

6

Hi

I’m running into the same issue using Podman/Kind/Helm. But for the looks of it, I’ll have no option to run everything using docker compose?

Cheers
Fré

7

What’s your CPU count? Elastic Search needs minimum 4CPU.

8

The CPU count for the node is 16.

9

Would you mind sharing more details.

  1. What version of Camunda are you trying out,
  2. What version of Linux OS are you using
  3. CPU and memory
  4. Issues in general, any logs

So that I can simulate in our lab and share the details.