Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flagd CrashLoopBackOff #1536

Closed
samuellvicente opened this issue Apr 17, 2024 · 2 comments · Fixed by open-telemetry/opentelemetry-helm-charts#1161
Closed

Flagd CrashLoopBackOff #1536

samuellvicente opened this issue Apr 17, 2024 · 2 comments · Fixed by open-telemetry/opentelemetry-helm-charts#1161
Labels
bug Something isn't working

Comments

@samuellvicente
Copy link

Bug Report

Which version of the demo you are using?
Version 1.9.0, deployed on a kind cluster

Symptom

Flagd deployment in CrashLoopBackOff

What is the expected behavior?
Flagd does not crash

What is the actual behavior?

Flagd in CrashLoopBackOff

Reproduce

Deploy the demo helm chart with Elastic values as per https://github.com/elastic/opentelemetry-demo

Additional Context

I suspect it is a issue of the memory limit being set to 20Mi, I bumped it to 100Mi and the issue was mitigated.

@samuellvicente samuellvicente added the bug Something isn't working label Apr 17, 2024
@puckpuck
Copy link
Contributor

puckpuck commented Apr 22, 2024

@samuellvicente can you do a kubectl describe pod <flagd-pod> and paste the output here?

@MadVikingGod
Copy link

I was running into the same problem. It looks like it's getting OOM killed because of the 20M limit. I upped it to 400M just to be safe and it starts fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants