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.
Possible changes needed to the base Galaxy Helm chart to allow backups to a Barman Object Store (cloud bucket). Some boilerplate for
VolumeSnapshotsis included, but is untested. Currently only Google Cloud Storage (GCS) is supported, but any cloud based storage provider (S3, Azure, etc.) could also be supported.How It Works (or doesn't as the case may be)
Two new blocks are added to the
postgresqlstanza in thevalues.yamlfile;backupandrecovery. If.Values.postgresql.backup.enabledis set totruethen abackupstanza is added when rendering the CNPGClusterobject. If.Values.postgresql.recovery.enabledis set totruearecoverystanza is included in theClusterdefinition.NOTE The bucket and any folders (
gs://your-bucket-name/galaxy-backupin this example) must already exist.Development versions of this chart (currently v6.1.1) are deployed to my own helm chart repostitory https://ksuderman.github.io/helm_charts. Simply add the following to the
values.yamlfor your GalaxyKubeman Helm chart: