Help with Error Code 137: OOMKiller When Deploying OpenLDAP in Rancher Desktop

0
8
Asked By CuriousCoder92 On

I'm running Kubernetes version 1.33.6 on Rancher Desktop version 1.22.0, with 6 CPUs and 32GB of RAM available. I'm trying to deploy Kubelauncher's OpenLDAP chart and currently have Authentik, PostgreSQL, and Valkey running under minimal load, consuming about 4.4GB of RAM total. I ran into an OOMKiller error, which is frustrating. I attempted to use jp-gouin's openldap-stack-ha Helm chart instead, but it still references Bitnami images in the values file, and I really don't want to dig for alternative container images for my dev setup. Has anyone successfully installed this OpenLDAP chart in Rancher Desktop without facing OOM errors?

2 Answers

Answered By TechGuru88 On

If you're getting an OOMKiller, that usually means your memory limits are set too low or your host just can't handle it. Can you check if you're hitting those limits? It could also be that your host doesn’t have enough available memory, even with what you've allocated.

Answered By DevNinja77 On

You mentioned not specifying memory limits, which is interesting. OpenLDAP shouldn't be a memory hog for a single replica. Given that your other services are consuming about 4.4GB, it sounds like there's more than enough to allocate. Maybe try adjusting your deployment settings to see if that helps avoid the OOM issue!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.