Conversation
Disable NATS clustering and reduce resource allocations so the CLI can schedule NATS on developer laptops without OOM or CPU pressure. Changes: - Disable NATS cluster mode (3 replicas → 1 single instance) - Memory: 1Gi → 512Mi per pod - CPU request: 500m → 100m (limit kept at 500m) - JetStream PVC: 20Gi → 5Gi - JetStream memory store max: 1Gi → 256Mi - Disable usageStats by default for local installs Closes ETL-943
ashish-bagri
approved these changes
Apr 1, 2026
sudopower
deleted the
kiran/etl-943-reduce-cli-defaults-for-nats-resources
branch
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
2 participants
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
Fixes ETL-943. Upstream NATS Helm chart defaults are 4 CPU / 3Gi memory per pod with 3 replicas — a total of 12 CPU and 9Gi memory. This causes scheduling failures on developer laptops running a local Kind cluster.
Test plan
glassflow upon a machine with limited resources (e.g. 8GB RAM laptop) and verify NATS pod schedules successfullyglassflow upcompletes (pipeline creation works)glassflow up --demoand confirm demo data flows end-to-end