Automated Etcd Backup and Restore for HyperShift Hosted Control Planes#2004
Automated Etcd Backup and Restore for HyperShift Hosted Control Planes#2004apahim wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
apahim
force-pushed
the
automated-backups
branch
2 times, most recently
from
eb2807d to
f3d9745
Compare
|
@apahim: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Ajpantuso
left a comment
Ajpantuso
left a comment
There was a problem hiding this comment.
Some general comments, but looks great!
This enhancement adds automated etcd backup to cloud storage and automatic restore on cluster creation for HyperShift hosted control planes. A CronJob periodically snapshots etcd and bundles the snapshot with critical PKI secrets and the etcd encryption key into a `.tar.gz` archive uploaded to cloud storage. When a new cluster is created with the same `infraID` and a backup exists, the snapshot and secrets are automatically restored. The standalone OCP automated etcd backup enhancement (`/enhancements/etcd/automated-backups.md`) explicitly lists HyperShift as a non-goal; this enhancement fills that gap. Signed-off-by: Amador Pahim <apahim@redhat.com>
2 participants
This enhancement adds automated etcd backup to cloud storage and automatic restore on cluster creation for HyperShift hosted control planes.
A CronJob periodically snapshots etcd and bundles the snapshot with critical PKI secrets and the etcd encryption key into a
.tar.gzarchive uploaded to cloud storage.When a new cluster is created with the same
infraIDand a backup exists, the snapshot and secrets are automatically restored.The standalone OCP automated etcd backup enhancement (
/enhancements/etcd/automated-backups.md) explicitly lists HyperShift as a non-goal; this enhancement fills that gap.