Support MySQL Backups and Restores #62
No reviewers
Labels
No labels
TUI
bug
docs
duplicate
enhancement
help wanted
invalid
major
question
secrets
wontfix
bug
duplicate
enhancement
help wanted
invalid
major
minor
patch
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
oeng/smol-k8s-lab!62
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/62/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
Supports backups and restores for MySQL databases
This came at the cost of needing to refine our schema a little bit. The app level
restoreschema has removed therestore.cnpg_restoreoption and therestoreschema now looks like this:This also obviates the need for maintaining PVCs specifically for MySQL, as the restore process now restores from S3 (typically seaweedfs right now).
We now have support for only restoring certain parts of an app. A full restore will still do everything, but you can conditionally just do s3, db, or pvc restores (or some combination).
We now always support adding the database hostname to your ExternalSecrets Provider
We support adding protocol to the issuer when saving the OIDC credentials to your ExternalSecrets provider (this only done for writefreely so far)
We now check to see if an OpenBao auth method for your app's namespace already exists instead of trying to create it again by default.