search

stellar / helm-charts

Helm charts for deploying SDF maintained software
3 stars 12 forks source link

charts/core: helm install, core pod has db init startup error #66

Closed sreuland closed 1 year ago

sreuland commented 1 year ago

What version are you using?

main

What did you do?

helm repo add stellar https://helm.stellar.org/charts && helm repo update stellar
helm install testcore stellar/core   --namespace sandbox   --set global.image.core.tag=19.13.1-1459.bf4363684.focal --set global.network=testnet --devel

What did you expect to see?

running core deployment on cluster

What did you see instead?


kubectl describe pod/testcore-0 -n sandbox
...
Init Containers:
  core-new-db:
    Container ID:  containerd://bc0038c94b191f2ad5302b5ee43ebc664fd74c93c02f0de0db7b38b1b91cd113
    Image:         docker.io/stellar/stellar-core:19.13.1-1459.bf4363684.focal
    Image ID:      docker.io/stellar/stellar-core@sha256:a8e293cb0cbdbbc548025ad1fd13dd4fef3160d55c7cdf6e75a9bbd9df62e4e4
    Port:          11626/TCP
    Host Port:     0/TCP
    Args:
      new-db
      --conf
      /config/stellar-core.cfg
      --console
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 31 Aug 2023 16:07:31 -0700
      Finished:     Thu, 31 Aug 2023 16:07:31 -0700
    Ready:          False
    Restart Count:  4
    Limits:
      cpu:     250m
      memory:  512Mi
    Requests:
      cpu:        100m
      memory:     256Mi
    Environment:  <none>
    Mounts:
      /config from core-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-n5zzb (ro)

...

Events:
  Type     Reason            Age                   From               Message
  ----     ------            ----                  ----               -------
  Normal   Scheduled         2m23s                 default-scheduler  Successfully assigned sandbox/testcore-0 to ip-172-22-24-82.ec2.internal
  Normal   Pulled            2m20s                 kubelet            Successfully pulled image "docker.io/stellar/stellar-core:19.13.1-1459.bf4363684.focal" in 1.973165104s
  Normal   Pulled            2m19s                 kubelet            Successfully pulled image "docker.io/stellar/stellar-core:19.13.1-1459.bf4363684.focal" in 102.370461ms
  Normal   Pulling           2m5s (x3 over 2m22s)  kubelet            Pulling image "docker.io/stellar/stellar-core:19.13.1-1459.bf4363684.focal"
  Normal   Created           2m5s (x3 over 2m20s)  kubelet            Created container core-new-db
  Normal   Started           2m5s (x3 over 2m20s)  kubelet            Started container core-new-db
  Normal   Pulled            2m5s                  kubelet            Successfully pulled image "docker.io/stellar/stellar-core:19.13.1-1459.bf4363684.focal" in 97.389568ms
  Warning  DNSConfigForming  110s (x9 over 2m22s)  kubelet            Search Line limits were exceeded, some search paths have been omitted, the applied search line is: sandbox.svc.cluster.local svc.cluster.local cluster.local dev.kube001.internal.stellar-ops.com internal.stellar-ops.com dev.services.stellar-ops.com
  Warning  BackOff           110s (x4 over 2m18s)  kubelet            Back-off restarting failed container
sreuland commented 1 year ago

I figured out the problem was values.yaml doesn't define a valid network core config by default, I had to use a copy of the provided futurenet-values.yaml which does have a valid config, I confirmed this worked:

helm install testcore stellar/core   \
--namespace sandbox  \
--set core.persistence.enabled=true \
--set global.image.core.tag=19.12.1-1406.b7d3a8f8d.focal-soroban \
--set global.image.core.repository=sreuland/stellar-core \
--set core.resources.limits.cpu=2 \
--set core.resources.limits.memory=4Gi \
--values charts/core/futurenet-values.yaml