Skip to content

reduce web out-of-memory (OOM) errors and enable Traefik JSON access logs. - #35

Merged
toto04 merged 1 commit into
mainfrom
fix/web-oom-traefik-access-logs
Nov 13, 2026
Merged

toto04 merged 1 commit into
mainfrom
fix/web-oom-traefik-access-logs

Conversation

@Leox1024

Copy link
Copy Markdown
Contributor

Summary

On November 12, 2026, the web pod restarted twice due to OOM (OOMKilled, exit code 137) with a 320Mi memory limit.

Kernel logs report libvips worker invoked oom-killer and the termination of next-server, indicating that image processing was active when the memory limit was exceeded. This strongly suggests that image processing contributed to the incident, but does not identify a specific image or prove that a particular /_next/image request was the root cause.

Prometheus's 15-second scrape interval may have missed short memory spikes. Traefik access logs were disabled, preventing request-level correlation.

Changes

  • Increase web memory limit from 320Mi to 512Mi.
  • Keep memory request unchanged at 160Mi.
  • Enable Traefik JSON access logs on stdout.
  • Exclude HTTP headers using logs.access.fields.headers.defaultmode: drop.
  • Keep Traefik's ClusterIP Service and all other settings unchanged.

Considerations

  • The increased limit mitigates memory spikes but does not fix potential memory leaks.
  • Traefik reconciliation may briefly interrupt ingress in the single-node cluster.
  • Access logs increase log volume and may contain client IPs and requested URLs. Retention and rotation remain unchanged.
  • Configuration is compatible with K3s v1.36.3+k3s1 and its bundled Traefik chart 40.1.4+up40.1.0.

Validation

  • YAML parsing and Kustomize rendering (v5.7.1).
  • ruby tests/workload-manifests.test.rb
  • ruby tests/redis-manifest.test.rb
  • Verified memory request (160Mi) and limit (512Mi).
  • Verified Traefik ClusterIP Service.
  • Verified JSON access logs, stdout output, and header exclusion against the bundled chart.

Post-deployment

  • Verify web memory settings and monitor OOM restarts.
  • Confirm Traefik availability and ingress connectivity.
  • Verify JSON access logs on stdout without HTTP headers.
  • Monitor log volume, rotation, and retention.

@coderabbitai

coderabbitai Bot commented Nov 12, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6b8afc93-3a09-4f63-ac91-32eb567bee87
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@Leox1024 Leox1024 changed the title Mitiga gli OOM di web e abilita gli access log JSON di Traefik reduce web out-of-memory (OOM) errors and enable Traefik JSON access logs. Nov 12, 2026
@toto04
toto04 merged commit 23c5310 into main Nov 13, 2026
2 checks passed
@Leox1024
Leox1024 deleted the fix/web-oom-traefik-access-logs branch November 17, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants