You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the postgres backup cronjob only allows the base postgres image to be used, which forces backups to use only postgres commands and store backups on a PVC.
What is the feature you are proposing to solve the problem?
If the cronjob backup allowed a configurable image, then a different and/or customized backup image and process could be executed depending on the target environment. For example, a container supporting wal-g and other remote connection tools could push WAL backups to a secure storage location outside of the cronjob PVC.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/postgres 16.4.2
What is the problem this feature will solve?
Currently, the postgres backup cronjob only allows the base postgres image to be used, which forces backups to use only postgres commands and store backups on a PVC.
What is the feature you are proposing to solve the problem?
If the cronjob backup allowed a configurable image, then a different and/or customized backup image and process could be executed depending on the target environment. For example, a container supporting wal-g and other remote connection tools could push WAL backups to a secure storage location outside of the cronjob PVC.
The text was updated successfully, but these errors were encountered: