Prerequisites
Code of Conduct
Feature Summary
The HealthEvents collection TTL and MongoDB PVC size are both hardcoded in the chart. At production write rates, the defaults exhaust storage in days and the TTL window is far longer than necessary. Neither can be changed without modifying the chart source.
Problem/Use Case
TTL: MONGODB_COLLECTION_EXPIRY_SECONDS is hardcoded to 2592000 (30 days) in charts/mongodb-store/templates/configmap.yaml. At 500 events/s with 350 bytes/doc, a 30-day TTL requires ~454 GB of storage. Reducing TTL to 7 days cuts this by 4.3× and proportionally reduces HEA query latency (P50 scales with collection size). Operators have no way to change this without patching the chart.
PVC: storage: "8Gi" is hardcoded in charts/mongodb-store/values.yaml. This is sized for development only. At any production write rate it exhausts in hours.
Proposed Solution
Expose both as Helm values with sensible defaults:
# mongodb-store/values.yaml
collectionExpirySeconds: 2592000 # 30 days default, operators should reduce to 604800 (7 days)
persistence:
size: "8Gi" # operators must size per fleet write rate
Wire collectionExpirySeconds into configmap.yaml and persistence.size into the PVC spec.
Expected improvement: Operators can reduce TTL to 7 days (4.3× smaller collection, proportional HEA latency reduction) and provision PVC appropriate for their fleet size — without touching chart source.
Component
Core Service
Prerequisites
Code of Conduct
Feature Summary
The HealthEvents collection TTL and MongoDB PVC size are both hardcoded in the chart. At production write rates, the defaults exhaust storage in days and the TTL window is far longer than necessary. Neither can be changed without modifying the chart source.
Problem/Use Case
TTL:
MONGODB_COLLECTION_EXPIRY_SECONDSis hardcoded to2592000(30 days) incharts/mongodb-store/templates/configmap.yaml. At 500 events/s with 350 bytes/doc, a 30-day TTL requires ~454 GB of storage. Reducing TTL to 7 days cuts this by 4.3× and proportionally reduces HEA query latency (P50 scales with collection size). Operators have no way to change this without patching the chart.PVC:
storage: "8Gi"is hardcoded incharts/mongodb-store/values.yaml. This is sized for development only. At any production write rate it exhausts in hours.Proposed Solution
Expose both as Helm values with sensible defaults:
Wire
collectionExpirySecondsintoconfigmap.yamlandpersistence.sizeinto the PVC spec.Expected improvement: Operators can reduce TTL to 7 days (4.3× smaller collection, proportional HEA latency reduction) and provision PVC appropriate for their fleet size — without touching chart source.
Component
Core Service