After further searching, I found this answer to another question, which recommended increasing container memory.
Initially I tested increased memory limits for Kibana when I started troubleshooting this issue. However, I only increased resources.limits.memory
, not resources.requests.memory
. Once I increased both, Kibana started up as expected. See the following settings:
resources:
requests:
cpu: "100m"
memory: "1Gi"
limits:
cpu: "1000m"
memory: "4Gi"
I suspect I may have increased the resources.limits.memory
by more than needed, but I'll continue adjusting it to see where it needs to be.