Comment 12 for bug 2051915

I tried applying the solution shown in the link @gboutry provided, I modified the statefull set to increase the delay to 300s and the timeout to 2s, and increasing the memory to 4GB but I still see the issue.

Anyway, if the issue was the liveness probe, Kubernetes shouldn't display an OOM error for the exit cause right?

    Command:
      /charm/bin/pebble
    Args:
      run
      --create-dirs
      --hold
      --http
      :38813
      --verbose
    State: Running
      Started: Wed, 06 Mar 2024 11:31:12 +0000
    Last State: Terminated
      Reason: Error
      Exit Code: 137
      Started: Wed, 06 Mar 2024 08:42:07 +0000
      Finished: Wed, 06 Mar 2024 11:31:12 +0000
    Ready: True
    Restart Count: 5
    Limits:
      memory: 4Gi
    Requests:
      memory: 4Gi
    Liveness: http-get http://:38813/v1/health%3Flevel=alive delay=300s timeout=2s period=5s #success=1 #failure=1
    Readiness: http-get http://:38813/v1/health%3Flevel=ready delay=30s timeout=1s period=5s #success=1 #failure=1