Repository navigation
Conversation
Provide a single-active Coordinator, four API replicas with required host separation, and persistent single-instance Redis as a sizing starting point. Keep small-installation defaults and existing worker/runtime behavior intact. Allow explicit Redis control-pool placement. Document SSD selection, the four-to-eight API capacity budget, safe existing-PVC expansion and rollback, and qualification required before claiming target sandbox or connection scale. Validate core and umbrella rendering, default compatibility and site overrides. Signed-off-by: wayne <rcywjo@gmail.com>
Move the profile rendering, host separation and Redis placement coverage into the chart contract suite already executed by CI. Remove the standalone test file and duplicated Redis/default-value assertions. Keep the capacity guide focused on reusable deployment and storage migration, clarify preservation of all immutable claim-template fields, and leave sizing values in the profile without implying an unmeasured scale guarantee. Signed-off-by: wayne <rcywjo@gmail.com>
This branch has not been deployed
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.
Add an opt-in core-chart capacity profile for larger installations while preserving lightweight defaults.
The profile configures one single-active Coordinator (4/8 CPU, 16/32Gi), four combined Ingress/API replicas (4/8 CPU, 8/16Gi each), and one persistent managed Redis instance (4/8 CPU, 32/64Gi) with AOF and a 200Gi PVC. API replicas require distinct hosts and can be expanded to eight after provisioning and qualifying the required capacity. Redis gains optional node selection, tolerations and affinity so it can use a stable control pool.
values-production.yamlowns the allocations. The deployment guide explains core/umbrella/Terraform consumption, host and memory budgets, explicit SSD StorageClass selection, maintenance and rollback. Existing StatefulSet claim-template fields must be retained; expanding a bound PVC or moving storage requires a separate reviewed procedure that preserves data and credentials.These are initial allocations, not a measured sandbox-count or connection-count guarantee. Single-instance Redis and Coordinator remain availability boundaries. No live cluster, runtime pins, credentials, API endpoints or worker scaling policies are changed.
Validation:
test_adx_chart.py, which existing CI already executes; no separate production test runner is added.