Repository navigation
reduce web out-of-memory (OOM) errors and enable Traefik JSON access logs. - #35
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
toto04
approved these changes
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
On November 12, 2026, the
webpod restarted twice due to OOM (OOMKilled, exit code137) with a320Mimemory limit.Kernel logs report
libvips worker invoked oom-killerand the termination ofnext-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/imagerequest 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
webmemory limit from320Mito512Mi.160Mi.logs.access.fields.headers.defaultmode: drop.ClusterIPService and all other settings unchanged.Considerations
v1.36.3+k3s1and its bundled Traefik chart40.1.4+up40.1.0.Validation
v5.7.1).ruby tests/workload-manifests.test.rbruby tests/redis-manifest.test.rb160Mi) and limit (512Mi).ClusterIPService.Post-deployment
webmemory settings and monitor OOM restarts.