Update flow-snapshot-worker-stateful-set.yaml #46
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.
🛠 Merge Request: Add missing configuration includes for Flow Snapshot Worker and bump chart versions
Summary
This merge request fixes the startup issue with the Flow Snapshot Worker in Kubernetes by adding missing configuration includes in the Helm chart, and also bumps the chart versions as required.
Fix Details
Added the following configuration includes under
peerdb-enterprise/peerdb/templates/flow-snapshot-worker-stateful-set.yaml:
These includes are necessary for:
MinIO access (aws.config)
PeerDB internal PostgreSQL catalog connection (catalog.pgConf)
Temporal configuration and connectivity (temporal.config)
Without them, the flow-snapshot-worker StatefulSet fails to start properly due to missing environment variables.
✅ Additional Updates (as requested)
Bumped both peerdb and peerdb-catalog chart versions according to semantic versioning.
Updated peerdb-catalog/values.yaml:
Set temporal.admintools.image.tag to match the correct version from the dependency in peerdb/Chart.yaml.
Result
After applying these changes:
The Flow Snapshot Worker now initializes successfully.
Chart versions and image tags are aligned with the project’s semantic versioning policy.