flagd and flagd-ui memory limits too low

[rcastley]

Bug Report

Which version of the demo you are using? v2.0.2

Symptom

Install the demo in k3s on a Multipass instance on Apple Silicon. The VM is configured with 4 CPUs, 8G RAM and 32Gb disk.

flagd is OOMKilled. Have tried both Helm chart and Kubernetes manifest.

What is the expected behavior?

flagd to start

What is the actual behavior?

flagd fails to start.

Reproduce

Use either the Helm chart or Kubernetes manifest from this repo.

Additional Context

By increasing the memory limit to 300Mi in the Kubernetes manifest for both flagd and flagd-ui the service starts with no issues.

[agardnerIT]

Hitting this too. Thanks for the investigation and fix!

flagd-5ddb9d9b66-p5gkj 1/2 OOMKilled 4 (2m8s ago) 22h

I was too keen. Still OOMKilled / CrashLoopBackOff.

Need to also increase flagd-ui via Helm. In case it helps someone:

values.yaml (extract)

components:
  flagd:
    useDefault:
      env: true
    resources:
      limits:
        memory: "300Mi"
    # flgad-ui as a sidecar container in the same pod so the flag json file can be shared
    sidecarContainers:
      - name: flagd-ui
        useDefault:
          env: true
        resources:
          limits:
            memory: "300Mi"

[julianocosta89]

Hey all, thx for reporting this!
We already have a PR on the Helm repo to update this, hopefully we can have that merged soon.