-
Notifications
You must be signed in to change notification settings - Fork 223
Conversation
@@ -510,6 +516,11 @@ spec: | |||
name: {{ template "timescaledb.fullname" . }}-pgbackrest | |||
defaultMode: 416 # 0640 permissions | |||
optional: true | |||
- name: pgbackrest-secrets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You just made this secret mandatory, not just for those wanting to enable GCS backups, but for everyone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be mandatory since line 523 is optional: true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I stand corrected. I didn't see that and didn't know about the optional
option.
Question: doesn't #389 affect this use case at all? |
Yes it does. #390 would fix this, but adds Azure documentation through comments in |
Yes, it would be preferable to get these changes coordinated (I am an Azure user myself). |
Would you suggest I wait to see how 390 shakes out, or just go ahead and add Azure to this PR? Seems like 390 is hung up on something unrelated. |
You should probably coordinate with its author. I'm just a concerned citizen :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work! 💯 Could you just fix those lint issues?
@gunnarsundberg Do you intend to finish this PR? I kinda need it. Let me know if I can help in any way, or if you'd like me to finish it myself. |
@agronholm I intend to finish it but have been quite busy. If you'd like it finished in the immediate future I'm cool with you doing it. If not I'll pick it back up at a later time 🙂 |
The easiest way would be if you granted me push access to your fork. Otherwise I could just copy everything to my fork and make a new PR, but I see that as unnecessary hassle. |
@paulfantom would you mind approving the test run? I believe I've fixed the issue. |
Is there anyway that we could rerun the tests to see the failure - would be nice to have this rolled into the main branch. |
Would also love to have this merged 🤞. We want to go to production soon on GKE and need support for backups to GCS. |
We're probably moving to the StackGres operator for deploying TimescaleDB. |
Signed-off-by: Gunnar Sundberg <[email protected]>
@gunnarsundberg can you fix the linting issues? Looks like you just need to bump the helm chart version.
|
@nhudson done! |
@gunnarsundberg looks like there is a lint issue and if you don't mind rebasing again? |
* add pgbackrest-secrets for gcs service key * add documentation for backing up to gcs * clean up gcs backup documentation and fix example * revert autogenerated toc changes * check for empty pgbackrest secret (for gcs) * remove s3 defaults and add examples for backup providers * add documentation for s3 azure and gcs changes * Fixed linting error * bump chart version * remove trailing space Signed-off-by: Gunnar Sundberg <[email protected]> Co-authored-by: Alex Grönholm <[email protected]>
pgBackRest already supports backups to GCS buckets and Azure Storage. This PR removes the default S3 config to allow for alternate providers, adds a simple method of configuring a GCP service account key through secrets, and documentation for how to configure the Helm Chart to use S3, GCS, or Azure.
Issue: #272 and #389