#kubernetes
help!! our Elasticsearch node runs in a container with a 256Mi memory limit. Several times a day it just dies: the status says OOMKilled, exit code 137. our dashborad says it uses well under teh limit most of teh time... how can it run out of memory? The app…
help!! small conifg change, rolled out to EKS, and now the frnotend pod is looping: rollback would be easy but i wanna undersatnd what happened. restart counter keeps clmibing and my on call phone is buzzing. The change was just a couple of environment…
small config cahnge, rolled out to AKS, and now the frontend pod is looping: rollback would be easy but I want to undrestand what happened :/ restart counter keeps climbing and my on call phone is buzzing. The change was just a couple of environment…
long time lurker first post lol were a agency running a couple of APIs and a database. Today its Docker Compose on two VMs, deployed by a script ;) A new hire is pushing hard for Kubernetes: self healing, rolling updates, industry satndard. I worry well…
ok weird one migrated the Node.js API from a VM to containres. On the VM it was fine for years. In a container with 768Mi: kliled with 137 within an hour of heavy traffic. same code, same traffic... what changed? on the VM, nothing ever complained. i suspect…
question for people who've been through it: for a agency with a couple of APIs and a database, did moving to Kubernetes pay off? i'm interested in the operatinoal reality: upgrades, debugging, on call, not the conference talk version. im not against…
help!! migrated the Go microservice from a VM to containers. On the VM it was fine for years. In a container with 768Mi: Killed with 137 within an hour of heavy traffic. Same code, same traffic. What changed? on the VM, nothing ever complained... i suspect…
so annoyed rn question for ppl whove been through it: for a internal IT team with a few internal tools, did moving to Kubernetes pay off? im interested in the operational reality: upgrades, debugging, on call, not teh conference talk version. im not against…
Deployed our cron job to GKE and it never becomes ready: kubectl get pods shows CrashLoopBackOff and a growing restart count. kubectl logs returns nothing at all. The same image runs fine with docker run on my laptop. Where do I look? The deployment manifest…
long time lurker first post lol deployed our worker pod to GKE and it never becomes ready: kubectl get pods shows CrashLoopBackOff and a growing restart count. kubectl logs returns nothing at all. The same image runs fine with docker run on my latpop. Where…
so annoyed rn deployed our database migration job to EKS and it never becomes ready: kubectl get pods shows CrashLoopBackOff and a growing restart count. kubectl logs returns nothing at all. The same image runs fine with docker run on my laptop. where do i…
help!! question for ppl whove been through it: for a two person team with client websites, did moving to Kubernetes pay off? im interested in the operational reality: upgrades, debugging, on call, not the conference talk version. im not against Kubernetes in…
i raised the limit for the Go microservice to 256Mi after teh first OOMKill. then it happened again: im afraid to just keep doubling it, my team lead asked is it a leak? 👍 and i honestly dont know how to tell. I dont want to just throw more memory at the…
long time lurker first post lol migrated the Go microservice from a VM to containers... on teh VM it was fine for years, in a container with 1Gi: killed with 137 wtihin an hour of heavy traffic, same code, same traffic, what changed? on the VM, nothing ever…
Were a small SaaS team running client websites. Today its Docker Compose on two VMs, deployed by a script 😂 A new hire is pushing hard for Kubernetes: self healing, rolling updates, industry standard. i worry well spend all our time running teh platform…
I raised the limit for the Python data job to 256Mi after the first OOMKill. Then it happened again: I'm afraid to just keep doubling it. My team lead asked 'is it a leak?' and I honestly don't know how to tell. I don't want to just throw more memory at the…
new to Kubernetes, please be gentle :D my frontend pod on k3s won't stay up: The status says CrashLoopBackOff... i googled it and it seems to just mean it crashes a lot. Thanks, Kubernetes. How do i find out WHY? i can see the pod, i can see the restart…
ugh. small config change, rolled out to k3s, and now the worker pod is looping: rollback would be easy but i want to understand what happened. restart counter keeps climbing and my on call phone is buzzing. The change was just a couple of environment…
ugh. were a agency running a handful of web apps 🔥 today its Docker Compose on two VMs, deployed by a script. A new hire is pushing hard for Kubernetes: self healing, rolling updates, industry standard. i worry well spend all our time running the platform…
new to Kubernetes, please be gentle. my database migration job on EKS wont stay up: the stauts says CrashLoopBackOff... i googled it and it seems to just mean it crashes alot.. :D thanks, Kubernetes... how do i find out WHY? I can see teh pod, I can see the…
i raised the limit for the PHP worker to 768Mi after the first OOMKill. Then it happened again: im afraid to just keep doubling it... my team lead asked is it a leak? and i honestly dont know how to tell. i dont want to just throw more memory at the problem…
i raised the limit for the Go microservice to 512Mi after the first OOMKill. Then it happened again: im afraid to just keep doubling it, my team lead asked is it a leak? and i honestly dont know how to tell. i don't want to just throw more memory at the…
