How to deploy camunda 8 in kubernetes using helm chart through microk8s

Hi community,

I’m trying to deploy camunda 8 in kubernetes using helm chart through microk8s

I have followed these steps

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

helm install <RELEASE_NAME> camunda/camunda-platform

The pods are not getting started

kubectl get pods -n camunda-example

NAME                                            READY   STATUS             RESTARTS        AGE
camunda-latest-connectors-76f9d58bf8-vm4q2      0/1     Running            6 (3m58s ago)   19m
camunda-latest-elasticsearch-master-0           0/1     Pending            0               19m
camunda-latest-elasticsearch-master-1           0/1     Pending            0               19m
camunda-latest-identity-7bc554455-68965         0/1     Pending            0               19m
camunda-latest-keycloak-0                       0/1     Running            5 (3m31s ago)   19m
camunda-latest-operate-7bc5cc95c5-kf9wf         0/1     CrashLoopBackOff   5 (27s ago)     19m
camunda-latest-optimize-f6978f946-2wgvd         0/1     Init:0/1           0               19m
camunda-latest-postgresql-0                     0/1     Pending            0               19m
camunda-latest-tasklist-5f598bcc9f-9n7pv        0/1     Pending            0               19m
camunda-latest-zeebe-0                          0/1     Pending            0               19m
camunda-latest-zeebe-1                          0/1     Pending            0               19m
camunda-latest-zeebe-2                          0/1     Pending            0               19m
camunda-latest-zeebe-gateway-7694fdc95f-6qnpx   1/1     Running            0               19m
camunda-latest-zeebe-gateway-7694fdc95f-8r4mp   0/1     Pending            0               19m

Is there anything that i need to configure before adding the installing the charts or am i missing anything

your insights would be helpful

Hi @Praveen_Kumar_Reddy - a lot depends on your environment, there isn’t a single solution. It could be a configuration issue, it could be a lack of resources, it could be something else entirely!

The error with Operate is very likely because Elasticsearch isn’t running yet, so I would try to troubleshoot the Elasticsearch pods first. I would first look at the events and logs for the two pods and see if anything stands out. Feel free to share the events and logs here too!

Thanks for your reply @nathan.loding ,

I’m new to kubernetes, I have followed the camunda way with the helm commands also followed the video mentioned in the youtube

I’m unable to get the pods running both ways, Is there any official video done by the camunda members to follow and deploy

Here are my pod running status and logs

root@Camunda-kube:~# kubectl get all -n camunda-helm
NAME                                                READY   STATUS     RESTARTS        AGE
pod/camunda-latest-connectors-76f9d58bf8-hbj8b      0/1     Pending    0               17m
pod/camunda-latest-elasticsearch-master-0           0/1     Pending    0               17m
pod/camunda-latest-elasticsearch-master-1           0/1     Pending    0               17m
pod/camunda-latest-identity-7bc554455-ppgtw         0/1     Running    5 (2m28s ago)   17m
pod/camunda-latest-keycloak-0                       0/1     Running    5 (3m12s ago)   17m
pod/camunda-latest-operate-7bc5cc95c5-2s5rl         0/1     Running    5 (3m10s ago)   17m
pod/camunda-latest-optimize-f6978f946-rqfbb         0/1     Init:0/1   0               17m
pod/camunda-latest-postgresql-0                     0/1     Pending    0               17m
pod/camunda-latest-tasklist-5f598bcc9f-7klkp        0/1     Running    5 (2m35s ago)   17m
pod/camunda-latest-zeebe-0                          0/1     Pending    0               17m
pod/camunda-latest-zeebe-1                          0/1     Pending    0               17m
pod/camunda-latest-zeebe-2                          0/1     Pending    0               17m
pod/camunda-latest-zeebe-gateway-7694fdc95f-jkp2r   0/1     Pending    0               17m
pod/camunda-latest-zeebe-gateway-7694fdc95f-vhc54   1/1     Running    0               17m

NAME                                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                        AGE
service/camunda-latest-connectors                ClusterIP   10.109.138.192   <none>        8080/TCP                       17m
service/camunda-latest-elasticsearch             ClusterIP   10.105.175.60    <none>        9200/TCP,9300/TCP              17m
service/camunda-latest-elasticsearch-master-hl   ClusterIP   None             <none>        9200/TCP,9300/TCP              17m
service/camunda-latest-identity                  ClusterIP   10.96.27.178     <none>        80/TCP,82/TCP                  17m
service/camunda-latest-keycloak                  ClusterIP   10.111.47.103    <none>        80/TCP                         17m
service/camunda-latest-keycloak-headless         ClusterIP   None             <none>        80/TCP                         17m
service/camunda-latest-operate                   ClusterIP   10.97.201.76     <none>        80/TCP                         17m
service/camunda-latest-optimize                  ClusterIP   10.110.133.130   <none>        80/TCP,8092/TCP                17m
service/camunda-latest-postgresql                ClusterIP   10.111.147.94    <none>        5432/TCP                       17m
service/camunda-latest-postgresql-hl             ClusterIP   None             <none>        5432/TCP                       17m
service/camunda-latest-tasklist                  ClusterIP   10.100.230.222   <none>        80/TCP                         17m
service/camunda-latest-zeebe                     ClusterIP   None             <none>        9600/TCP,26502/TCP,26501/TCP   17m
service/camunda-latest-zeebe-gateway             ClusterIP   10.100.150.85    <none>        9600/TCP,26500/TCP             17m

NAME                                           READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/camunda-latest-connectors      0/1     1            0           17m
deployment.apps/camunda-latest-identity        0/1     1            0           17m
deployment.apps/camunda-latest-operate         0/1     1            0           17m
deployment.apps/camunda-latest-optimize        0/1     1            0           17m
deployment.apps/camunda-latest-tasklist        0/1     1            0           17m
deployment.apps/camunda-latest-zeebe-gateway   1/2     2            1           17m

NAME                                                      DESIRED   CURRENT   READY   AGE
replicaset.apps/camunda-latest-connectors-76f9d58bf8      1         1         0       17m
replicaset.apps/camunda-latest-identity-7bc554455         1         1         0       17m
replicaset.apps/camunda-latest-operate-7bc5cc95c5         1         1         0       17m
replicaset.apps/camunda-latest-optimize-f6978f946         1         1         0       17m
replicaset.apps/camunda-latest-tasklist-5f598bcc9f        1         1         0       17m
replicaset.apps/camunda-latest-zeebe-gateway-7694fdc95f   2         2         1       17m

NAME                                                   READY   AGE
statefulset.apps/camunda-latest-elasticsearch-master   0/2     17m
statefulset.apps/camunda-latest-keycloak               0/1     17m
statefulset.apps/camunda-latest-postgresql             0/1     17m
statefulset.apps/camunda-latest-zeebe                  0/3     17m

root@Camunda-kube:~# kubectl logs camunda-latest-keycloak-0 -n camunda-helm
Defaulted container "keycloak" out of: keycloak, copy-camunda-theme (init), copy-configs (init)
keycloak 13:44:44.28 INFO  ==>
keycloak 13:44:44.28 INFO  ==> Welcome to the Bitnami keycloak container
keycloak 13:44:44.28 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
keycloak 13:44:44.28 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
keycloak 13:44:44.28 INFO  ==>
keycloak 13:44:44.28 INFO  ==> ** Starting keycloak setup **
keycloak 13:44:44.29 INFO  ==> Validating settings in KEYCLOAK_* env vars...
keycloak 13:44:44.34 INFO  ==> Trying to connect to PostgreSQL server camunda-latest-postgresql...
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
timeout reached before the port went into state "inuse"
keycloak 13:47:14.44 ERROR ==> Unable to connect to host camunda-latest-postgresql


root@Camunda-kube:~# kubectl logs camunda-latest-identity-7bc554455-ppgtw -n camunda-helm
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v3.1.6)

2023-12-15 14:02:45.441  INFO 1 --- [           main] i.c.i.Application                        : Starting Application using Java 17.0.9 with PID 1 (/app/identity.jar started by identity in /app)
2023-12-15 14:02:45.452  INFO 1 --- [           main] i.c.i.Application                        : The following 1 profile is active: "keycloak"
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2023-12-15 14:02:48.445  WARN 1 --- [           main] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: io.camunda.identity.config.IdentityCommon
2023-12-15 14:02:48.467  WARN 1 --- [           main] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: io.camunda.identity.security.spring.filter.FilterExceptionHandler
2023-12-15 14:02:48.825  WARN 1 --- [           main] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: io.camunda.identity.impl.keycloak.config.record.KeycloakClient
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2023-12-15 14:02:50.536  INFO 1 --- [           main] i.c.i.Application                        : Started Application in 6.082 seconds (process running for 7.331)
2023-12-15 14:02:51.673 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #1. Unable to connect to Keycloak.
2023-12-15 14:03:16.519  WARN 1 --- [nio-8082-exec-1] o.s.w.s.h.HandlerMappingIntrospector     : Cache miss for REQUEST dispatch to '/actuator/health' (previous null). Performing CorsConfiguration lookup. This is logged once only at WARN level, and every time at TRACE.
2023-12-15 14:03:16.530  WARN 1 --- [nio-8082-exec-1] o.s.w.s.h.HandlerMappingIntrospector     : Cache miss for REQUEST dispatch to '/actuator/health' (previous null). Performing MatchableHandlerMapping lookup. This is logged once only at WARN level, and every time at TRACE.
2023-12-15 14:03:21.674  WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
2023-12-15 14:03:22.701 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #2. Unable to connect to Keycloak.
2023-12-15 14:03:52.702  WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
2023-12-15 14:03:53.710 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #3. Unable to connect to Keycloak.
2023-12-15 14:04:23.710  WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
2023-12-15 14:04:24.718 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #4. Unable to connect to Keycloak.
2023-12-15 14:04:54.719  WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
2023-12-15 14:04:55.730 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #5. Unable to connect to Keycloak.
2023-12-15 14:05:25.731  WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
2023-12-15 14:05:26.766 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #6. Unable to connect to Keycloak.
2023-12-15 14:05:26.766 ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : RESTEASY004655: Unable to invoke request: org.apache.http.conn.HttpHostConnectException: Connect to camunda-latest-keycloak:80 [camunda-latest-keycloak/10.111.47.103] failed: Connection refused

@Praveen_Kumar_Reddy - we don’t have an official guide for microk8s, but we do have one for kind. The process should be similar.

The latest logs you’ve shared are somewhat expected: Identity (the last set of logs) has a dependency on Keycloak (the middle set) which has a dependency on Postgres, which is still Pending (first set).

To troubleshoot this you need to go pod by pod, in order of dependency. Postgres and Elasticsearch are the two pods that don’t have any dependencies, so that’s why I would start with those. What do the logs for those two pods say? I would also look at the events for those. I would not troubleshoot or look at any other pods until those two are up and running - it’s entirely possible that once those are running, everything else starts!

@nathan.loding Thanks for your guidance, It really helped me.

I have tried deploying helm in kind cluster by the normal way without applying any other yaml on top of it.

helm install camunda-platform camunda/camunda-platform

It was able to start the postgres and keycloak,

root@Camunda-kube:/# kubectl get all
NAME                                                 READY   STATUS             RESTARTS   AGE
pod/camunda-platform-connectors-bff84f94-bqzp8       0/1     CrashLoopBackOff   7          31m
pod/camunda-platform-elasticsearch-master-0          0/1     Running            7          31m
pod/camunda-platform-elasticsearch-master-1          0/1     Pending            0          31m
pod/camunda-platform-identity-5954886d87-hldqp       0/1     Pending            0          31m
pod/camunda-platform-keycloak-0                      1/1     Running            0          31m
pod/camunda-platform-operate-6fb4f5c87-b4f8v         0/1     Pending            0          31m
pod/camunda-platform-optimize-5865c7bf8d-mk7vf       0/1     Pending            0          31m
pod/camunda-platform-postgresql-0                    1/1     Running            0          31m
pod/camunda-platform-tasklist-746f74b468-5clpd       0/1     Running            7          31m
pod/camunda-platform-zeebe-0                         0/1     Pending            0          31m
pod/camunda-platform-zeebe-1                         0/1     Pending            0          31m
pod/camunda-platform-zeebe-2                         0/1     Pending            0          31m
pod/camunda-platform-zeebe-gateway-66cc87db7-ltbn5   0/1     Pending            0          31m
pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5   1/1     Running            0          31m

NAME                                               TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                        AGE
service/camunda-platform-connectors                ClusterIP   10.96.172.211   <none>        8080/TCP                       31m
service/camunda-platform-elasticsearch             ClusterIP   10.96.131.109   <none>        9200/TCP,9300/TCP              31m
service/camunda-platform-elasticsearch-master-hl   ClusterIP   None            <none>        9200/TCP,9300/TCP              31m
service/camunda-platform-identity                  ClusterIP   10.96.107.82    <none>        80/TCP,82/TCP                  31m
service/camunda-platform-keycloak                  ClusterIP   10.96.151.243   <none>        80/TCP                         31m
service/camunda-platform-keycloak-headless         ClusterIP   None            <none>        80/TCP                         31m
service/camunda-platform-operate                   ClusterIP   10.96.239.232   <none>        80/TCP                         31m
service/camunda-platform-optimize                  ClusterIP   10.96.47.4      <none>        80/TCP,8092/TCP                31m
service/camunda-platform-postgresql                ClusterIP   10.96.205.128   <none>        5432/TCP                       31m
service/camunda-platform-postgresql-hl             ClusterIP   None            <none>        5432/TCP                       31m
service/camunda-platform-tasklist                  ClusterIP   10.96.183.95    <none>        80/TCP                         31m
service/camunda-platform-zeebe                     ClusterIP   None            <none>        9600/TCP,26502/TCP,26501/TCP   31m
service/camunda-platform-zeebe-gateway             ClusterIP   10.96.46.14     <none>        9600/TCP,26500/TCP             31m
service/kubernetes                                 ClusterIP   10.96.0.1       <none>        443/TCP                        83m

NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/camunda-platform-connectors      0/1     1            0           31m
deployment.apps/camunda-platform-identity        0/1     1            0           31m
deployment.apps/camunda-platform-operate         0/1     1            0           31m
deployment.apps/camunda-platform-optimize        0/1     1            0           31m
deployment.apps/camunda-platform-tasklist        0/1     1            0           31m
deployment.apps/camunda-platform-zeebe-gateway   1/2     2            1           31m

NAME                                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/camunda-platform-connectors-bff84f94       1         1         0       31m
replicaset.apps/camunda-platform-identity-5954886d87       1         1         0       31m
replicaset.apps/camunda-platform-operate-6fb4f5c87         1         1         0       31m
replicaset.apps/camunda-platform-optimize-5865c7bf8d       1         1         0       31m
replicaset.apps/camunda-platform-tasklist-746f74b468       1         1         0       31m
replicaset.apps/camunda-platform-zeebe-gateway-66cc87db7   2         2         1       31m

NAME                                                     READY   AGE
statefulset.apps/camunda-platform-elasticsearch-master   0/2     31m
statefulset.apps/camunda-platform-keycloak               1/1     31m
statefulset.apps/camunda-platform-postgresql             1/1     31m
statefulset.apps/camunda-platform-zeebe                  0/3     31m
root@Camunda-kube:/# kubectl get pvc
NAME                                           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-camunda-platform-elasticsearch-master-0   Bound     pvc-0d0989f6-7d6b-402e-9b36-bf481b1cb88c   64Gi       RWO            standard       31m
data-camunda-platform-elasticsearch-master-1   Pending                                                                        standard       31m
data-camunda-platform-postgresql-0             Bound     pvc-af669ffe-9bd8-41e1-8413-a660d4c8660b   8Gi        RWO            standard       31m
data-camunda-platform-zeebe-0                  Pending                                                                        standard       31m
data-camunda-platform-zeebe-1                  Pending                                                                        standard       31m
data-camunda-platform-zeebe-2                  Pending                                                                        standard       31m

Logs of postgres

root@Camunda-kube:/# kubectl logs camunda-platform-postgresql-0
postgresql 11:37:58.78 INFO  ==>
postgresql 11:37:58.78 INFO  ==> Welcome to the Bitnami postgresql container
postgresql 11:37:58.78 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 11:37:58.78 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 11:37:58.79 INFO  ==>
postgresql 11:37:58.81 INFO  ==> ** Starting PostgreSQL setup **
postgresql 11:37:58.83 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 11:37:58.85 INFO  ==> Loading custom pre-init scripts...
postgresql 11:37:58.86 INFO  ==> Initializing PostgreSQL database...
postgresql 11:37:58.89 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 11:37:58.89 INFO  ==> Generating local authentication configuration
grep: /opt/bitnami/postgresql/conf/postgresql.conf: No such file or directory
postgresql 11:37:59.53 INFO  ==> Starting PostgreSQL in background...
postgresql 11:37:59.74 INFO  ==> Changing password of postgres
postgresql 11:37:59.78 INFO  ==> Creating user bn_keycloak
postgresql 11:37:59.80 INFO  ==> Granting access to "bn_keycloak" to the database "bitnami_keycloak"
postgresql 11:37:59.82 INFO  ==> Setting ownership for the 'public' schema database "bitnami_keycloak" to "bn_keycloak"
postgresql 11:37:59.84 INFO  ==> Configuring replication parameters
postgresql 11:37:59.86 INFO  ==> Configuring synchronous_replication
postgresql 11:37:59.86 INFO  ==> Configuring fsync
postgresql 11:37:59.89 INFO  ==> Stopping PostgreSQL...
waiting for server to shut down.... done
server stopped
postgresql 11:38:00.00 INFO  ==> Loading custom scripts...
postgresql 11:38:00.01 INFO  ==> Enabling remote connections

postgresql 11:38:00.02 INFO  ==> ** PostgreSQL setup finished! **
postgresql 11:38:00.06 INFO  ==> ** Starting PostgreSQL **
2023-12-16 11:38:00.085 GMT [1] LOG:  pgaudit extension initialized
2023-12-16 11:38:00.091 GMT [1] LOG:  starting PostgreSQL 15.5 on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-12-16 11:38:00.092 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-12-16 11:38:00.092 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2023-12-16 11:38:00.093 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2023-12-16 11:38:00.096 GMT [138] LOG:  database system was shut down at 2023-12-16 11:37:59 GMT
2023-12-16 11:38:00.104 GMT [1] LOG:  database system is ready to accept connections
2023-12-16 11:38:55.555 GMT [208] ERROR:  relation "migration_model" does not exist at character 25
2023-12-16 11:38:55.555 GMT [208] STATEMENT:  SELECT ID, VERSION FROM MIGRATION_MODEL ORDER BY UPDATE_TIME DESC
2023-12-16 11:38:58.849 GMT [208] ERROR:  relation "public.databasechangelog" does not exist at character 22
2023-12-16 11:38:58.849 GMT [208] STATEMENT:  SELECT COUNT(*) FROM public.databasechangelog
2023-12-16 11:38:59.168 GMT [226] ERROR:  relation "public.databasechangeloglock" does not exist at character 22
2023-12-16 11:38:59.168 GMT [226] STATEMENT:  SELECT COUNT(*) FROM public.databasechangeloglock
2023-12-16 11:38:59.198 GMT [208] ERROR:  relation "public.databasechangelog" does not exist at character 22
2023-12-16 11:38:59.198 GMT [208] STATEMENT:  SELECT COUNT(*) FROM public.databasechangelog
2023-12-16 11:43:00.195 GMT [136] LOG:  checkpoint starting: time
2023-12-16 11:43:54.918 GMT [136] LOG:  checkpoint complete: wrote 548 buffers (3.3%); 1 WAL file(s) added, 0 removed, 0 recycled; write=54.681 s, sync=0.005 s, total=54.724 s; sync files=552, longest=0.001 s, average=0.001 s; distance=3807 kB, estimate=3807 kB

Logs of Keycloak

root@Camunda-kube:/# kubectl logs camunda-platform-keycloak-0
Defaulted container "keycloak" out of: keycloak, copy-camunda-theme (init), copy-configs (init)
keycloak 11:38:41.99 INFO  ==>
keycloak 11:38:41.99 INFO  ==> Welcome to the Bitnami keycloak container
keycloak 11:38:41.99 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
keycloak 11:38:42.00 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
keycloak 11:38:42.00 INFO  ==>
keycloak 11:38:42.00 INFO  ==> ** Starting keycloak setup **
keycloak 11:38:42.02 INFO  ==> Validating settings in KEYCLOAK_* env vars...
keycloak 11:38:42.04 INFO  ==> Trying to connect to PostgreSQL server camunda-platform-postgresql...
keycloak 11:38:42.05 INFO  ==> Found PostgreSQL server listening at camunda-platform-postgresql:5432
keycloak 11:38:42.05 INFO  ==> Configuring database settings
keycloak 11:38:42.09 INFO  ==> Enabling statistics
keycloak 11:38:42.10 INFO  ==> Enabling health endpoints
keycloak 11:38:42.11 INFO  ==> Configuring http settings
keycloak 11:38:42.12 INFO  ==> Configuring hostname settings
keycloak 11:38:42.13 INFO  ==> Configuring cache count
keycloak 11:38:42.14 INFO  ==> Configuring log level
keycloak 11:38:42.15 INFO  ==> Configuring proxy
keycloak 11:38:42.17 INFO  ==> ** keycloak setup finished! **

keycloak 11:38:42.20 INFO  ==> ** Starting keycloak **
Appending additional Java properties to JAVA_OPTS: -Djgroups.dns.query=camunda-platform-keycloak-headless.default.svc.cluster.local
Updating the configuration and installing your custom providers, if any. Please wait.
2023-12-16 11:38:45,795 WARN  [org.keycloak.services] (build-9) KC-SERVICES0047: metrics (org.jboss.aerogear.keycloak.metrics.MetricsEndpointFactory) is implementing the internal SPI realm-restapi-extension. This SPI is internal and may change without notice
2023-12-16 11:38:46,164 WARN  [org.keycloak.services] (build-9) KC-SERVICES0047: metrics-listener (org.jboss.aerogear.keycloak.metrics.MetricsEventListenerFactory) is implementing the internal SPI eventsListener. This SPI is internal and may change without notice
2023-12-16 11:38:50,838 INFO  [io.quarkus.deployment.QuarkusAugmentor] (main) Quarkus augmentation completed in 6556ms
2023-12-16 11:38:52,548 INFO  [org.keycloak.quarkus.runtime.hostname.DefaultHostnameProvider] (main) Hostname settings: Base URL: <unset>, Hostname: <request>, Strict HTTPS: false, Path: <request>, Strict BackChannel: false, Admin URL: <unset>, Admin: <request>, Port: -1, Proxied: true
2023-12-16 11:38:54,350 WARN  [io.quarkus.agroal.runtime.DataSources] (main) Datasource <default> enables XA but transaction recovery is not enabled. Please enable transaction recovery by setting quarkus.transaction-manager.enable-recovery=true, otherwise data may be lost if the application is terminated abruptly
2023-12-16 11:38:55,250 WARN  [org.infinispan.PERSISTENCE] (keycloak-cache-init) ISPN000554: jboss-marshalling is deprecated and planned for removal
2023-12-16 11:38:55,354 INFO  [org.infinispan.CONTAINER] (keycloak-cache-init) ISPN000556: Starting user marshaller 'org.infinispan.jboss.marshalling.core.JBossUserMarshaller'
2023-12-16 11:38:55,528 WARN  [io.quarkus.vertx.http.runtime.VertxHttpRecorder] (main) The X-Forwarded-* and Forwarded headers will be considered when determining the proxy address. This configuration can cause a security issue as clients can forge requests and send a forwarded header that is not overwritten by the proxy. Please consider use one of these headers just to forward the proxy address in requests.
2023-12-16 11:38:55,643 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000078: Starting JGroups channel `ISPN` with stack `kubernetes`
2023-12-16 11:38:55,646 INFO  [org.jgroups.JChannel] (keycloak-cache-init) local_addr: 2411b3fa-d833-46f8-ae42-7ed9ef9d08fc, name: camunda-platform-keycloak-0-27484
2023-12-16 11:38:55,659 INFO  [org.jgroups.protocols.FD_SOCK2] (keycloak-cache-init) server listening on *.57800
2023-12-16 11:38:57,675 INFO  [org.jgroups.protocols.pbcast.GMS] (keycloak-cache-init) camunda-platform-keycloak-0-27484: no members discovered after 2005 ms: creating cluster as coordinator
2023-12-16 11:38:57,685 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000094: Received new cluster view for channel ISPN: [camunda-platform-keycloak-0-27484|0] (1) [camunda-platform-keycloak-0-27484]
2023-12-16 11:38:57,773 INFO  [org.infinispan.CLUSTER] (keycloak-cache-init) ISPN000079: Channel `ISPN` local address is `camunda-platform-keycloak-0-27484`, physical addresses are `[10.244.0.11:7800]`
2023-12-16 11:38:57,800 WARN  [org.infinispan.CONFIG] (keycloak-cache-init) ISPN000569: Unable to persist Infinispan internal caches as no global state enabled
2023-12-16 11:38:59,200 INFO  [org.keycloak.quarkus.runtime.storage.legacy.liquibase.QuarkusJpaUpdaterProvider] (main) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml

UPDATE SUMMARY
Run:                        115
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:          115

2023-12-16 11:39:03,997 INFO  [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (main) Node name: camunda-platform-keycloak-0-27484, Site name: null
2023-12-16 11:39:04,107 INFO  [org.keycloak.broker.provider.AbstractIdentityProviderMapper] (main) Registering class org.keycloak.broker.provider.mappersync.ConfigSyncEventListener
2023-12-16 11:39:04,126 INFO  [org.keycloak.services] (main) KC-SERVICES0050: Initializing master realm
2023-12-16 11:39:06,390 INFO  [io.quarkus] (main) Keycloak 22.0.5 on JVM (powered by Quarkus 3.2.7.Final) started in 15.419s. Listening on: http://0.0.0.0:8080
2023-12-16 11:39:06,390 INFO  [io.quarkus] (main) Profile dev activated.
2023-12-16 11:39:06,391 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, jdbc-h2, jdbc-mariadb, jdbc-mssql, jdbc-mysql, jdbc-oracle, jdbc-postgresql, keycloak, logging-gelf, micrometer, narayana-jta, reactive-routes, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, vertx]
2023-12-16 11:39:06,609 INFO  [org.keycloak.services] (main) KC-SERVICES0009: Added user 'admin' to realm 'master'
2023-12-16 11:39:06,614 WARN  [org.keycloak.quarkus.runtime.KeycloakMain] (main) Running the server in development mode. DO NOT use this configuration in production.

Logs of Elasticsearch

root@Camunda-kube:/# kubectl logs camunda-platform-elasticsearch-master-0
Defaulted container "elasticsearch" out of: elasticsearch, sysctl (init)
elasticsearch 12:13:50.27
elasticsearch 12:13:50.28 Welcome to the Bitnami elasticsearch container
elasticsearch 12:13:50.28 Subscribe to project updates by watching https://github.com/bitnami/containers
elasticsearch 12:13:50.28 Submit issues and feature requests at https://github.com/bitnami/containers/issues
elasticsearch 12:13:50.28
elasticsearch 12:13:50.28 INFO  ==> ** Starting Elasticsearch setup **
elasticsearch 12:13:50.33 WARN  ==> Setting ELASTICSEARCH_IS_DEDICATED_NODE is disabled.
elasticsearch 12:13:50.33 WARN  ==> ELASTICSEARCH_NODE_ROLES will be ignored and Elasticsearch will asume all different roles.
elasticsearch 12:13:50.34 INFO  ==> Configuring/Initializing Elasticsearch...
elasticsearch 12:13:50.37 INFO  ==> Setting default configuration
elasticsearch 12:13:50.42 INFO  ==> Configuring Elasticsearch cluster settings...
warning: ignoring JAVA_HOME=/opt/bitnami/java; using ES_JAVA_HOME
elasticsearch 12:13:51.93 INFO  ==> ** Elasticsearch setup finished! **

elasticsearch 12:13:51.97 INFO  ==> ** Starting Elasticsearch **
warning: ignoring JAVA_HOME=/opt/bitnami/java; using ES_JAVA_HOME
[2023-12-16T12:13:55,438][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] version[8.8.2], pid[319], build[tar/98e1271edf932a480e4262a471281f1ee295ce6b/2023-06-26T05:16:16.196344851Z], OS[Linux/5.15.0-91-generic/amd64], JVM[BellSoft/OpenJDK 64-Bit Server VM/17.0.8/17.0.8+7-LTS]
[2023-12-16T12:13:55,439][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] JVM home [/opt/bitnami/java], using bundled JDK [false]
[2023-12-16T12:13:55,440][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] JVM arguments [-Des.networkaddress.cache.ttl=60, -Des.networkaddress.cache.negative.ttl=10, -Djava.security.manager=allow, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Dlog4j2.formatMsgNoLookups=true, -Djava.locale.providers=SPI,COMPAT, --add-opens=java.base/java.io=org.elasticsearch.preallocate, -XX:+UseG1GC, -Djava.io.tmpdir=/tmp/elasticsearch-3235617345869157180, -XX:+HeapDumpOnOutOfMemoryError, -XX:+ExitOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,level,pid,tags:filecount=32,filesize=64m, -Xms1024m, -Xmx1024m, -XX:MaxDirectMemorySize=536870912, -XX:G1HeapRegionSize=4m, -XX:InitiatingHeapOccupancyPercent=30, -XX:G1ReservePercent=15, -Des.distribution.type=tar, --module-path=/opt/bitnami/elasticsearch/lib, --add-modules=jdk.net, --add-modules=org.elasticsearch.preallocate, -Djdk.module.main=org.elasticsearch.server]
[2023-12-16T12:13:57,409][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: No SLF4J providers were found.
[2023-12-16T12:13:57,409][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: Defaulting to no-operation (NOP) logger implementation
[2023-12-16T12:13:57,410][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
[2023-12-16T12:13:57,410][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
[2023-12-16T12:13:57,410][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: Ignoring binding found at [jar:file:///opt/bitnami/elasticsearch/modules/repository-azure/log4j-slf4j-impl-2.19.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[2023-12-16T12:13:57,411][WARN ][stderr                   ] [camunda-platform-elasticsearch-master-0] SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
[2023-12-16T12:13:58,558][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [repository-url]
[2023-12-16T12:13:58,558][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [dlm]
[2023-12-16T12:13:58,558][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-core]
[2023-12-16T12:13:58,558][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-redact]
[2023-12-16T12:13:58,558][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [ingest-user-agent]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-async-search]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-monitoring]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [repository-s3]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-analytics]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-ent-search]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-autoscaling]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [lang-painless]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-ml]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [legacy-geo]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [lang-mustache]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-ql]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [rank-rrf]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [analysis-common]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [transport-netty4]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [aggregations]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [ingest-common]
[2023-12-16T12:13:58,559][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [frozen-indices]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-identity-provider]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-shutdown]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-text-structure]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [snapshot-repo-test-kit]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [ml-package-loader]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [kibana]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [constant-keyword]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-logstash]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-ccr]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-graph]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [parent-join]
[2023-12-16T12:13:58,560][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-enrich]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [repositories-metering-api]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [transform]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [repository-azure]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [repository-gcs]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [spatial]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [mapper-extras]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [mapper-version]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [apm]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-aggregate-metric]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-rollup]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [percolator]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [data-streams]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-stack]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [rank-eval]
[2023-12-16T12:13:58,561][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [reindex]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-security]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [blob-cache]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [searchable-snapshots]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [snapshot-based-recoveries]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-watcher]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [old-lucene-versions]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-ilm]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-voting-only-node]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-deprecation]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-fleet]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-profiling]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [ingest-geoip]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-write-load-forecaster]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [search-business-rules]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [ingest-attachment]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [wildcard]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [unsigned-long]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-sql]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-async]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [runtime-fields-common]
[2023-12-16T12:13:58,562][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [vector-tile]
[2023-12-16T12:13:58,563][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [lang-expression]
[2023-12-16T12:13:58,563][INFO ][o.e.p.PluginsService     ] [camunda-platform-elasticsearch-master-0] loaded module [x-pack-eql]
[2023-12-16T12:14:01,415][INFO ][o.e.e.NodeEnvironment    ] [camunda-platform-elasticsearch-master-0] using [1] data paths, mounts [[/bitnami/elasticsearch/data (/dev/mapper/ubuntu--vg-ubuntu--lv)]], net usable_space [57.1gb], net total_space [97.8gb], types [ext4]
[2023-12-16T12:14:01,415][INFO ][o.e.e.NodeEnvironment    ] [camunda-platform-elasticsearch-master-0] heap size [1gb], compressed ordinary object pointers [true]
[2023-12-16T12:14:01,456][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] node name [camunda-platform-elasticsearch-master-0], node ID [ge7x1oQsS3uZqbFTzZWU6g], cluster name [elastic], roles [ingest, data_frozen, ml, data_hot, transform, data_content, data_warm, master, remote_cluster_client, data, data_cold]
[2023-12-16T12:14:03,876][INFO ][o.e.x.s.Security         ] [camunda-platform-elasticsearch-master-0] Security is disabled
[2023-12-16T12:14:04,118][INFO ][o.e.x.p.ProfilingPlugin  ] [camunda-platform-elasticsearch-master-0] Profiling is enabled
[2023-12-16T12:14:04,578][INFO ][o.e.t.n.NettyAllocator   ] [camunda-platform-elasticsearch-master-0] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=1mb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=true, g1gc_region_size=4mb, heap_size=1gb}]
[2023-12-16T12:14:04,598][INFO ][o.e.i.r.RecoverySettings ] [camunda-platform-elasticsearch-master-0] using rate limit [40mb] with [default=40mb, read=0b, write=0b, max=0b]
[2023-12-16T12:14:04,642][INFO ][o.e.d.DiscoveryModule    ] [camunda-platform-elasticsearch-master-0] using discovery type [multi-node] and seed hosts providers [settings]
[2023-12-16T12:14:05,418][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] initialized
[2023-12-16T12:14:05,419][INFO ][o.e.n.Node               ] [camunda-platform-elasticsearch-master-0] starting ...
[2023-12-16T12:14:05,429][INFO ][o.e.x.s.c.f.PersistentCache] [camunda-platform-elasticsearch-master-0] persistent cache index loaded
[2023-12-16T12:14:05,430][INFO ][o.e.x.d.l.DeprecationIndexingComponent] [camunda-platform-elasticsearch-master-0] deprecation component started
[2023-12-16T12:14:05,519][INFO ][o.e.t.TransportService   ] [camunda-platform-elasticsearch-master-0] publish_address {camunda-platform-elasticsearch-master-0.camunda-platform-elasticsearch-master-hl.default.svc.cluster.local/10.244.0.15:9300}, bound_addresses {[::]:9300}
[2023-12-16T12:14:05,644][INFO ][o.e.b.BootstrapChecks    ] [camunda-platform-elasticsearch-master-0] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2023-12-16T12:14:05,646][INFO ][o.e.c.c.ClusterBootstrapService] [camunda-platform-elasticsearch-master-0] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to [camunda-platform-elasticsearch-master-0, camunda-platform-elasticsearch-master-1]
[2023-12-16T12:14:15,656][WARN ][o.e.c.c.ClusterFormationFailureHelper] [camunda-platform-elasticsearch-master-0] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [camunda-platform-elasticsearch-master-0, camunda-platform-elasticsearch-master-1] to bootstrap a cluster: have discovered [{camunda-platform-elasticsearch-master-0}{ge7x1oQsS3uZqbFTzZWU6g}{AfSMgefXT7W34IbXjUxLbw}{camunda-platform-elasticsearch-master-0}{camunda-platform-elasticsearch-master-0.camunda-platform-elasticsearch-master-hl.default.svc.cluster.local}{10.244.0.15:9300}{cdfhilmrstw}{8.8.2}]; discovery will continue using [] from hosts providers and [{camunda-platform-elasticsearch-master-0}{ge7x1oQsS3uZqbFTzZWU6g}{AfSMgefXT7W34IbXjUxLbw}{camunda-platform-elasticsearch-master-0}{camunda-platform-elasticsearch-master-0.camunda-platform-elasticsearch-master-hl.default.svc.cluster.local}{10.244.0.15:9300}{cdfhilmrstw}{8.8.2}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.8/discovery-troubleshooting.html
[2023-12-16T12:14:25,659][WARN ][o.e.c.c.ClusterFormationFailureHelper] [camunda-platform-elasticsearch-master-0] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [camunda-platform-elasticsearch-master-0, camunda-platform-elasticsearch-master-1] to bootstrap a cluster: have discovered [{camunda-platform-elasticsearch-master-0}{ge7x1oQsS3uZqbFTzZWU6g}{AfSMgefXT7W34IbXjUxLbw}{camunda-platform-elasticsearch-master-0}{camunda-platform-elasticsearch-master-0.camunda-platform-elasticsearch-master-hl.default.svc.cluster.local}{10.244.0.15:9300}{cdfhilmrstw}{8.8.2}]; discovery will continue using [] from hosts providers and [{camunda-platform-elasticsearch-master-0}{ge7x1oQsS3uZqbFTzZWU6g}{AfSMgefXT7W34IbXjUxLbw}{camunda-platform-elasticsearch-master-0}{camunda-platform-elasticsearch-master-0.camunda-platform-elasticsearch-master-hl.default.svc.cluster.local}{10.244.0.15:9300}{cdfhilmrstw}{8.8.2}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.8/discovery-troubleshooting.html


No logs for identity

Below are the logs of events

48m         Normal    Killing                 pod/camunda-platform-connectors-5ff9995fb4-rzmgb                     Stopping container connectors
29m         Normal    Scheduled               pod/camunda-platform-connectors-bff84f94-bqzp8                       Successfully assigned default/camunda-platform-connectors-bff84f94-bqzp8 to kind-control-plane
22m         Normal    Pulled                  pod/camunda-platform-connectors-bff84f94-bqzp8                       Container image "camunda/connectors-bundle:8.3.2" already present on machine
22m         Normal    Created                 pod/camunda-platform-connectors-bff84f94-bqzp8                       Created container connectors
22m         Normal    Started                 pod/camunda-platform-connectors-bff84f94-bqzp8                       Started container connectors
3m35s       Warning   Unhealthy               pod/camunda-platform-connectors-bff84f94-bqzp8                       Readiness probe failed: Get "http://10.244.0.9:8080/actuator/health/readiness": dial tcp 10.244.0.9:8080: connect: connection refused
8m49s       Warning   BackOff                 pod/camunda-platform-connectors-bff84f94-bqzp8                       Back-off restarting failed container
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-connectors-bff84f94                      Created pod: camunda-platform-connectors-bff84f94-bqzp8
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-connectors                               Scaled up replica set camunda-platform-connectors-bff84f94 to 1
49m         Warning   FailedScheduling        pod/camunda-platform-elasticsearch-master-0                          0/1 nodes are available: 1 Insufficient cpu.
48m         Warning   FailedScheduling        pod/camunda-platform-elasticsearch-master-0                          skip schedule deleting pod: default/camunda-platform-elasticsearch-master-0
28m         Normal    Scheduled               pod/camunda-platform-elasticsearch-master-0                          Successfully assigned default/camunda-platform-elasticsearch-master-0 to kind-control-plane
28m         Normal    Pulling                 pod/camunda-platform-elasticsearch-master-0                          Pulling image "docker.io/bitnami/os-shell:11-debian-11-r92"
28m         Normal    Pulled                  pod/camunda-platform-elasticsearch-master-0                          Successfully pulled image "docker.io/bitnami/os-shell:11-debian-11-r92" in 16.768348294s
28m         Normal    Created                 pod/camunda-platform-elasticsearch-master-0                          Created container sysctl
28m         Normal    Started                 pod/camunda-platform-elasticsearch-master-0                          Started container sysctl
28m         Normal    Pulling                 pod/camunda-platform-elasticsearch-master-0                          Pulling image "docker.io/bitnami/elasticsearch:8.8.2"
27m         Normal    Pulled                  pod/camunda-platform-elasticsearch-master-0                          Successfully pulled image "docker.io/bitnami/elasticsearch:8.8.2" in 1m37.374966304s
27m         Normal    Created                 pod/camunda-platform-elasticsearch-master-0                          Created container elasticsearch
27m         Normal    Started                 pod/camunda-platform-elasticsearch-master-0                          Started container elasticsearch
25m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:40:58.11 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
25m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:08.12 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
25m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:18.11 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:28.12 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:38.11 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:48.12 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:41:58.12 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:42:08.11 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
24m         Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m11:42:18.13 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
3m28s       Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          (combined from similar events): Readiness probe failed: ^[[38;5;6melasticsearch ^[[38;5;5m12:02:58.11 ^[[0m^[[38;5;2mINFO ^[[0m ==> Checking Elasticsearch health...
8m48s       Warning   Unhealthy               pod/camunda-platform-elasticsearch-master-0                          Liveness probe failed: dial tcp 10.244.0.15:9200: connect: connection refused
49m         Warning   FailedScheduling        pod/camunda-platform-elasticsearch-master-1                          0/1 nodes are available: 1 Insufficient cpu.
48m         Warning   FailedScheduling        pod/camunda-platform-elasticsearch-master-1                          skip schedule deleting pod: default/camunda-platform-elasticsearch-master-1
62s         Warning   FailedScheduling        pod/camunda-platform-elasticsearch-master-1                          0/1 nodes are available: 1 Insufficient cpu.
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-elasticsearch-master                    create Claim data-camunda-platform-elasticsearch-master-0 Pod camunda-platform-elasticsearch-master-0 in StatefulSet camunda-platform-elasticsearch-master success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-elasticsearch-master                    create Pod camunda-platform-elasticsearch-master-0 in StatefulSet camunda-platform-elasticsearch-master successful
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-elasticsearch-master                    create Claim data-camunda-platform-elasticsearch-master-1 Pod camunda-platform-elasticsearch-master-1 in StatefulSet camunda-platform-elasticsearch-master success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-elasticsearch-master                    create Pod camunda-platform-elasticsearch-master-1 in StatefulSet camunda-platform-elasticsearch-master successful
32s         Warning   FailedScheduling        pod/camunda-platform-identity-5954886d87-hldqp                       0/1 nodes are available: 1 Insufficient cpu.
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-identity-5954886d87                      Created pod: camunda-platform-identity-5954886d87-hldqp
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-identity                                 Scaled up replica set camunda-platform-identity-5954886d87 to 1
29m         Normal    Scheduled               pod/camunda-platform-keycloak-0                                      Successfully assigned default/camunda-platform-keycloak-0 to kind-control-plane
29m         Normal    Pulling                 pod/camunda-platform-keycloak-0                                      Pulling image "camunda/identity:8.3.4"
28m         Normal    Pulled                  pod/camunda-platform-keycloak-0                                      Successfully pulled image "camunda/identity:8.3.4" in 13.485097948s
28m         Normal    Created                 pod/camunda-platform-keycloak-0                                      Created container copy-camunda-theme
28m         Normal    Started                 pod/camunda-platform-keycloak-0                                      Started container copy-camunda-theme
28m         Normal    Pulling                 pod/camunda-platform-keycloak-0                                      Pulling image "bitnami/keycloak:22.0.5"
27m         Normal    Pulled                  pod/camunda-platform-keycloak-0                                      Successfully pulled image "bitnami/keycloak:22.0.5" in 1m4.097457247s
27m         Normal    Created                 pod/camunda-platform-keycloak-0                                      Created container copy-configs
27m         Normal    Started                 pod/camunda-platform-keycloak-0                                      Started container copy-configs
27m         Normal    Pulled                  pod/camunda-platform-keycloak-0                                      Container image "docker.io/bitnami/keycloak:22.0.5" already present on machine
27m         Normal    Created                 pod/camunda-platform-keycloak-0                                      Created container keycloak
27m         Normal    Started                 pod/camunda-platform-keycloak-0                                      Started container keycloak
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-keycloak                                create Pod camunda-platform-keycloak-0 in StatefulSet camunda-platform-keycloak successful
2s          Warning   FailedScheduling        pod/camunda-platform-operate-6fb4f5c87-b4f8v                         0/1 nodes are available: 1 Insufficient cpu.
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-operate-6fb4f5c87                        Created pod: camunda-platform-operate-6fb4f5c87-b4f8v
51m         Warning   BackOff                 pod/camunda-platform-operate-85dc77d67-q7kzh                         Back-off restarting failed container
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-operate                                  Scaled up replica set camunda-platform-operate-6fb4f5c87 to 1
32s         Warning   FailedScheduling        pod/camunda-platform-optimize-5865c7bf8d-mk7vf                       0/1 nodes are available: 1 Insufficient cpu.
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-optimize-5865c7bf8d                      Created pod: camunda-platform-optimize-5865c7bf8d-mk7vf
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-optimize                                 Scaled up replica set camunda-platform-optimize-5865c7bf8d to 1
28m         Normal    Scheduled               pod/camunda-platform-postgresql-0                                    Successfully assigned default/camunda-platform-postgresql-0 to kind-control-plane
28m         Normal    Pulling                 pod/camunda-platform-postgresql-0                                    Pulling image "docker.io/bitnami/postgresql:15.5.0"
28m         Normal    Pulled                  pod/camunda-platform-postgresql-0                                    Successfully pulled image "docker.io/bitnami/postgresql:15.5.0" in 28.680372245s
28m         Normal    Created                 pod/camunda-platform-postgresql-0                                    Created container postgresql
28m         Normal    Started                 pod/camunda-platform-postgresql-0                                    Started container postgresql
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-postgresql                              create Claim data-camunda-platform-postgresql-0 Pod camunda-platform-postgresql-0 in StatefulSet camunda-platform-postgresql success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-postgresql                              create Pod camunda-platform-postgresql-0 in StatefulSet camunda-platform-postgresql successful
29m         Normal    Scheduled               pod/camunda-platform-tasklist-746f74b468-5clpd                       Successfully assigned default/camunda-platform-tasklist-746f74b468-5clpd to kind-control-plane
20m         Normal    Pulled                  pod/camunda-platform-tasklist-746f74b468-5clpd                       Container image "camunda/tasklist:8.3.4" already present on machine
20m         Normal    Created                 pod/camunda-platform-tasklist-746f74b468-5clpd                       Created container tasklist
23m         Normal    Started                 pod/camunda-platform-tasklist-746f74b468-5clpd                       Started container tasklist
18m         Warning   Unhealthy               pod/camunda-platform-tasklist-746f74b468-5clpd                       Readiness probe failed: Get "http://10.244.0.10:8080/actuator/health/readiness": dial tcp 10.244.0.10:8080: connect: connection refused
3m50s       Warning   BackOff                 pod/camunda-platform-tasklist-746f74b468-5clpd                       Back-off restarting failed container
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-tasklist-746f74b468                      Created pod: camunda-platform-tasklist-746f74b468-5clpd
51m         Warning   BackOff                 pod/camunda-platform-tasklist-76bd7bcf58-q4pgn                       Back-off restarting failed container
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-tasklist                                 Scaled up replica set camunda-platform-tasklist-746f74b468 to 1
49m         Warning   FailedScheduling        pod/camunda-platform-zeebe-0                                         0/1 nodes are available: 1 Insufficient cpu.
48m         Warning   FailedScheduling        pod/camunda-platform-zeebe-0                                         skip schedule deleting pod: default/camunda-platform-zeebe-0
32s         Warning   FailedScheduling        pod/camunda-platform-zeebe-0                                         0/1 nodes are available: 1 Insufficient cpu.
62s         Warning   FailedScheduling        pod/camunda-platform-zeebe-1                                         0/1 nodes are available: 1 Insufficient cpu.
32s         Warning   FailedScheduling        pod/camunda-platform-zeebe-2                                         0/1 nodes are available: 1 Insufficient cpu.
32s         Warning   FailedScheduling        pod/camunda-platform-zeebe-gateway-66cc87db7-ltbn5                   0/1 nodes are available: 1 Insufficient cpu.
29m         Normal    Scheduled               pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5                   Successfully assigned default/camunda-platform-zeebe-gateway-66cc87db7-pjbw5 to kind-control-plane
29m         Normal    Pulled                  pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5                   Container image "camunda/zeebe:8.3.4" already present on machine
29m         Normal    Created                 pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5                   Created container zeebe-gateway
29m         Normal    Started                 pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5                   Started container zeebe-gateway
28m         Warning   Unhealthy               pod/camunda-platform-zeebe-gateway-66cc87db7-pjbw5                   Readiness probe failed: Get "http://10.244.0.12:9600/actuator/health/readiness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-zeebe-gateway-66cc87db7                  Created pod: camunda-platform-zeebe-gateway-66cc87db7-pjbw5
29m         Normal    SuccessfulCreate        replicaset/camunda-platform-zeebe-gateway-66cc87db7                  Created pod: camunda-platform-zeebe-gateway-66cc87db7-ltbn5
48m         Normal    Killing                 pod/camunda-platform-zeebe-gateway-768cd66989-jxlr4                  Stopping container zeebe-gateway
29m         Normal    ScalingReplicaSet       deployment/camunda-platform-zeebe-gateway                            Scaled up replica set camunda-platform-zeebe-gateway-66cc87db7 to 2
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Claim data-camunda-platform-zeebe-0 Pod camunda-platform-zeebe-0 in StatefulSet camunda-platform-zeebe success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Pod camunda-platform-zeebe-0 in StatefulSet camunda-platform-zeebe successful
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Claim data-camunda-platform-zeebe-1 Pod camunda-platform-zeebe-1 in StatefulSet camunda-platform-zeebe success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Pod camunda-platform-zeebe-1 in StatefulSet camunda-platform-zeebe successful
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Claim data-camunda-platform-zeebe-2 Pod camunda-platform-zeebe-2 in StatefulSet camunda-platform-zeebe success
29m         Normal    SuccessfulCreate        statefulset/camunda-platform-zeebe                                   create Pod camunda-platform-zeebe-2 in StatefulSet camunda-platform-zeebe successful
51m         Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-elasticsearch-master-0   waiting for pod camunda-platform-elasticsearch-master-0 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-elasticsearch-master-0   waiting for first consumer to be created before binding
29m         Normal    ExternalProvisioning    persistentvolumeclaim/data-camunda-platform-elasticsearch-master-0   waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manually created by system administrator
29m         Normal    Provisioning            persistentvolumeclaim/data-camunda-platform-elasticsearch-master-0   External provisioner is provisioning volume for claim "default/data-camunda-platform-elasticsearch-master-0"
28m         Normal    ProvisioningSucceeded   persistentvolumeclaim/data-camunda-platform-elasticsearch-master-0   Successfully provisioned volume pvc-0d0989f6-7d6b-402e-9b36-bf481b1cb88c
51m         Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-elasticsearch-master-1   waiting for pod camunda-platform-elasticsearch-master-1 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-elasticsearch-master-1   waiting for first consumer to be created before binding
4m4s        Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-elasticsearch-master-1   waiting for pod camunda-platform-elasticsearch-master-1 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-postgresql-0             waiting for first consumer to be created before binding
29m         Normal    ExternalProvisioning    persistentvolumeclaim/data-camunda-platform-postgresql-0             waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manually created by system administrator
29m         Normal    Provisioning            persistentvolumeclaim/data-camunda-platform-postgresql-0             External provisioner is provisioning volume for claim "default/data-camunda-platform-postgresql-0"
28m         Normal    ProvisioningSucceeded   persistentvolumeclaim/data-camunda-platform-postgresql-0             Successfully provisioned volume pvc-af669ffe-9bd8-41e1-8413-a660d4c8660b
51m         Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-zeebe-0                  waiting for pod camunda-platform-zeebe-0 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-zeebe-0                  waiting for first consumer to be created before binding
4m4s        Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-zeebe-0                  waiting for pod camunda-platform-zeebe-0 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-zeebe-1                  waiting for first consumer to be created before binding
4m4s        Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-zeebe-1                  waiting for pod camunda-platform-zeebe-1 to be scheduled
29m         Normal    WaitForFirstConsumer    persistentvolumeclaim/data-camunda-platform-zeebe-2                  waiting for first consumer to be created before binding
4m4s        Normal    WaitForPodScheduled     persistentvolumeclaim/data-camunda-platform-zeebe-2                  waiting for pod camunda-platform-zeebe-2 to be scheduled

Hi @Praveen_Kumar_Reddy - if you look at the last set of logs you provided, you’ll see a common message: 0/1 nodes are available: 1 Insufficient cpu.

In order words, Docker doesn’t have enough resources to start all the pods. You can try to increase the amount of resources you’ve given Docker, or you can scale back the deployment. To scale back the deployment, you can look at altering the default CPU/RAM resources for each service (here’s the defaults for Zeebe, for instance) by overriding the resources property in your local values.yaml file. You can also scale back the number of brokers, partitions, etc.

What is you goal with installing this locally? To have a functional environment to develop against? To understand how deploy Camunda with Kubernetes/Helm?

Hi @nathan.loding ,

Sorry for the delay in getting back to you. I appreciate your guidance! I’ve been diving into Kubernetes and Helm charts, and I now have a solid understanding of these topics. Additionally, I’ve explored Camunda deployment through Helm. Thanks again for your assistance!

1 Like