bramblefox
@bramblefox
Regular
Regular · Member since Oct 2026
0 followers · 0 following
- Topics created
- 3
- Posts created
- 8
- Likes given
- 3
- Likes received
- 2
- Days visited
- 0
- Solutions
- 1
Days visited count across the whole community, not just this forum.
Most active topics
- Burrow CLI: disable upgrade checks
3 replies · 0 votes
- Node.js app memory climbs until OOM — only on Larkhost
2 replies · 0 votes
- Network policies: can egress rules cover ICMP and the internal DNS resolver?
2 replies · 0 votes
Most liked posts
- Burrow CLI: disable upgrade checks
Every lark burrow command checks for a CLI update first, which adds ~400 ms in CI. Is there a flag or environment variable to turn that off?
2 likes
- Blue-green deploy seems to keep adding more pods
I seem to remember that min_pods_running = 0 does not play well with blue-green: the old (blue) pods are stopped rather than destroyed, so they are not counted
1 likes
Top categories
Top tags
- #burrows 1
- #javascript 1
- #memory 1
- #networking 1
- #wishlist 1
- Node.js app memory climbs until OOM — only on Larkhost
Node sizes its heap from the machine, not the container, on some versions. Set NODE_OPTIONS=--max-old-space-size=384 and see if it levels out.
Likes given · 10/12/2026
- Deploying a Django app with background workers: what is the cleanest setup?
Exactly one beat is the bit I would have got wrong. Thank you.
Likes given · 10/12/2026
- Burrow CLI: disable upgrade checks
Liked by gilbertw
Every lark burrow command checks for a CLI update first, which adds ~400 ms in CI. Is there a flag or environment variable to turn that off?
Likes received · 10/12/2026
- Burrow CLI: disable upgrade checks
Liked by nadia_k
Every lark burrow command checks for a CLI update first, which adds ~400 ms in CI. Is there a flag or environment variable to turn that off?
Likes received · 10/12/2026
- Pod restarts by itself 1–3 minutes after waking from idle
Reproducible: let the app autostop, send one request, and between one and three minutes later the pod restarts. Exit code is 137. Memory graph shows nothing nea
Likes given · 10/12/2026
- Node.js app memory climbs until OOM — only on Larkhost
Flat at 240 MB after a day. That was it.
Replies · 10/12/2026
- Node.js app memory climbs until OOM — only on Larkhost
Locally, memory is flat at ~180 MB. On a 512 MB pod it climbs to the limit over six hours and the pod is killed.
Topics · 10/12/2026
- Laravel queues stop processing after a deploy
Are you caching config at build time? php artisan queue:restart writes a timestamp to the cache, and if the worker reads a stale cache it never sees it.
Replies · 10/12/2026
- Show & Tell: a tiny job runner on pods that sleep between jobs
Suspend instead of stop is the clever bit — resumes are much faster than cold boots.
Replies · 10/11/2026
- Network policies: can egress rules cover ICMP and the internal DNS resolver?
Clear, thanks.
Replies · 10/10/2026
- Network policies: can egress rules cover ICMP and the internal DNS resolver?
We want to deny all egress except our database and the internal resolver. Are ICMP and DNS to the resolver covered by egress rules, or always allowed?
Topics · 10/10/2026
- Burrow CLI: disable upgrade checks
Every lark burrow command checks for a CLI update first, which adds ~400 ms in CI. Is there a flag or environment variable to turn that off?
Topics · 10/9/2026
- New pods that mount a secret as a file are destroyed within one second
Is the secret base64-encoded? File secrets are decoded before writing, and if decoding fails the pod is torn down before your process starts — which is why ther
Replies · 10/8/2026
- Pods can now be cordoned before a deploy
Finally. We were scaling to zero and back just to drain one pod.
Replies · 10/7/2026