vector (the log collector) reads the log files of every pod on the node, so its memory need follows the node's log volume. At 256 MiB it was killed for running out of memory 122 times on instance 1 and used 89% on instance 2. New instances now get a 512 MiB limit (request unchanged at 128 MiB).
Total limit per instance 5.625 -> 5.875 GiB; requests stay 1.875 GiB. README table and the totals test updated.
Version 1.1.1 -> 1.1.2.
The two running instances were already patched by hand to 512 MiB.
- vector (the log collector) reads the log files of every pod on the node, so its memory need follows the node's log volume. At 256 MiB it was killed for running out of memory 122 times on instance 1 and used 89% on instance 2. New instances now get a 512 MiB limit (request unchanged at 128 MiB).
- Total limit per instance 5.625 -> 5.875 GiB; requests stay 1.875 GiB. README table and the totals test updated.
- Version 1.1.1 -> 1.1.2.
The two running instances were already patched by hand to 512 MiB.
Nothing here is a breaking change.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
- vector reads the log files of every pod on the node, so its memory need follows the node's log volume. At
256 MiB it was killed for running out of memory 122 times on instance 1 and used 89% on instance 2.
The limit is now 512 MiB (request unchanged at 128 MiB) for new instances; the total limit per instance
goes from 5.625 GiB to 5.875 GiB, requests stay at 1.875 GiB.
- README memory table and the test for the totals updated
- version 1.1.1 -> 1.1.2
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
igor
merged commit b86863e6f0 into main2026-09-19 09:56:36 +00:00
igor
deleted branch fix/vector-memory-limit2026-09-19 09:56:36 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The two running instances were already patched by hand to 512 MiB.
Nothing here is a breaking change.
🤖 Generated with Claude Code