Skip to content

[ENG-4138]: Make Memgraph snapshot retention count configurable#345

Open
anatoly-scherbakov wants to merge 3 commits into
mainfrom
anatoly-eng-4138-increase-snapshot-count
Open

[ENG-4138]: Make Memgraph snapshot retention count configurable#345
anatoly-scherbakov wants to merge 3 commits into
mainfrom
anatoly-eng-4138-increase-snapshot-count

Conversation

@anatoly-scherbakov

Copy link
Copy Markdown
Contributor

What

Make the Memgraph snapshot retention count configurable instead of relying on Memgraph's unbounded default.

  • Add snapshotRetentionCount: 32 to charts/datafold/charts/memgraph/values.yaml.
  • Render --storage-snapshot-retention-count={{ .Values.snapshotRetentionCount }} in the StatefulSet args (charts/datafold/charts/memgraph/templates/statefulset.yaml).

Why

The Memgraph container args were hardcoded and did not cap snapshot retention, so on-disk snapshots could grow unbounded. This caps retention at 32 by default and lets deployments tune it.

Override

Deployments can override via the operator's rawValues, which map straight onto subchart values:

memgraph:
  rawValues:
    snapshotRetentionCount: 64

Verification

helm template through the parent chart renders the new arg:

args:
  - "--storage-snapshot-on-exit=true"
  - "--storage-snapshot-retention-count=32"
  - "--log-level=WARNING"
  - "--also-log-to-stderr=true"

Overriding memgraph.snapshotRetentionCount=64 renders --storage-snapshot-retention-count=64.

No chart version bumps (memgraph dependency is pinned as *.*.* in the parent).

🤖 Generated with Claude Code

Add --storage-snapshot-retention-count to the Memgraph StatefulSet args,
defaulting to 32 via a new snapshotRetentionCount value so deployments can
override it through rawValues.memgraph instead of relying on the unbounded
default.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🔍 Kubeconform Validation Results

All cloud provider configurations passed Kubernetes API schema validation!

Cloud Provider Status
AWS ✅ Passed
GCP ✅ Passed
Azure ✅ Passed

The rendered Kubernetes manifests conform to the Kubernetes API specification across all cloud providers.

Required by ct lint version-bump gate for the Memgraph snapshot retention change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🔍 Kubeconform Validation Results

All cloud provider configurations passed Kubernetes API schema validation!

Cloud Provider Status
AWS ✅ Passed
GCP ✅ Passed
Azure ✅ Passed

The rendered Kubernetes manifests conform to the Kubernetes API specification across all cloud providers.

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🔍 Kubeconform Validation Results

All cloud provider configurations passed Kubernetes API schema validation!

Cloud Provider Status
AWS ✅ Passed
GCP ✅ Passed
Azure ✅ Passed

The rendered Kubernetes manifests conform to the Kubernetes API specification across all cloud providers.

Comment thread CLAUDE.md Outdated
@datafold datafold deleted a comment from anatoly-scherbakov Jun 9, 2026
Source .env only when it exists so direnv stops erroring on a fresh checkout.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

🔍 Kubeconform Validation Results

All cloud provider configurations passed Kubernetes API schema validation!

Cloud Provider Status
AWS ✅ Passed
GCP ✅ Passed
Azure ✅ Passed

The rendered Kubernetes manifests conform to the Kubernetes API specification across all cloud providers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants