feat(sentry): add db cleanup #1875
Open
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.
This pull request adds support for automated database cleanup of the
nodestore_node
table in Sentry's Helm chart. It introduces a new configurable cron job that performs SQL deletion and vacuuming to reclaim space, with options for scheduling, resource management, and environment setup. The changes are documented in the chart's README and are configurable viavalues.yaml
.Database Cleanup CronJob Feature:
cronjob-sentry-db-cleanup.yaml
) that runs SQL commands to delete old records and vacuum thenodestore_node
table, with support for scheduling, resource limits, and environment variables.values.yaml
undersentry.cleanup.dbCleanup
to control the cron job's schedule, image, resources, and other settings.dbCleanup
configuration options for users.Environment Variable Handling:
sentry.postgresql.env
) to correctly set PostgreSQL environment variables for the cleanup job, supporting both internal and external database secrets.