camunda-community-hub / camunda-7-community-helm

Camunda public Kubernetes Helm repo and charts
Apache License 2.0
39 stars 38 forks source link

Not working #1

Closed abdel1979 closed 3 years ago

abdel1979 commented 3 years ago

Hello i deploy the helm chart; but the pod wont start, here is the describe of the pods 👍 Any help much appreciated


kubectl describe pods/camunda-camunda-bpm-platform-xxxx 
Name:         camunda-camunda-bpm-platform-xxxx
Namespace:   xxxx
Priority:     0
Node:         xxxx
Start Time:   Tue, 13 Apr 2021 19:26:18 +0000
Labels:       app.kubernetes.io/instance=camunda
              app.kubernetes.io/name=camunda-bpm-platform
              pod-template-hash=xxxx
Annotations:  <none>
Status:       Running
IP:           xxx
IPs:
  IP:           xxx
Controlled By:  ReplicaSet/camunda-camunda-bpm-platform-xxx
Containers:
  camunda-bpm-platform:
    Container ID:   docker://xxx
    Image:          camunda/camunda-bpm-platform:tomcat-latest
    Image ID:       docker-pullable://camunda/camunda-bpm-platform@sha256:xxx
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Tue, 13 Apr 2021 19:26:19 +0000
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     200m
      memory:  256Mi
    Requests:
      cpu:      200m
      memory:   256Mi
    Readiness:  http-get http://:http/camunda/ delay=60s timeout=1s period=60s #success=1 #failure=3
    Environment:
      DEBUG:           false
      JMX_PROMETHEUS:  false
      DB_DRIVER:       org.postgresql.Driver
      DB_URL:          jdbc:postgresql://camunda-db-postgresql.svc.cluster.local:5432/camundadb
      DB_USERNAME:     <set to the key 'DB_USERNAME' in secret 'camunda-postgre-creds'>  Optional: false
      DB_PASSWORD:     <set to the key 'DB_PASSWORD' in secret 'camunda-postgre-creds'>  Optional: false
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from camunda-camunda-bpm-platform-token-xxx (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  camunda-camunda-bpm-platform-token-xxx:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  camunda-camunda-bpm-platform-token-xxx
    Optional:    false
QoS Class:       Guaranteed
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age   From               Message
  ----     ------     ----  ----               -------
  Normal   Scheduled  104s  default-scheduler  Successfully assigned dev-ops/camunda-camunda-bpm-platform-xxx to xxx
  Normal   Pulled     103s  kubelet            Container image "camunda/camunda-bpm-platform:tomcat-latest" already present on machine
  Normal   Created    103s  kubelet            Created container camunda-bpm-platform
  Normal   Started    103s  kubelet            Started container camunda-bpm-platform
  Warning  Unhealthy  34s   kubelet            Readiness probe failed: Get http://xxx:8080/camunda/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
aabouzaid commented 3 years ago

Hi @abdel1979 Could you please provide more details about your setup as well as your values.yaml file.

aabouzaid commented 3 years ago

No updates since then, so please use the new release v1.0.0 it has some fixes related to the startup of the pods.