Skip to content

[OSDOCS-12142]: Adding backup/restore docs for HCP on OpenShift Virt#84179

Merged
lahinson merged 1 commit intoopenshift:mainfrom
lahinson:osdocs-12142-backup-restore-hcp-kubevirt
Nov 6, 2024
Merged

[OSDOCS-12142]: Adding backup/restore docs for HCP on OpenShift Virt#84179
lahinson merged 1 commit intoopenshift:mainfrom
lahinson:osdocs-12142-backup-restore-hcp-kubevirt

Conversation

@lahinson
Copy link
Contributor

@lahinson lahinson commented Oct 28, 2024

Version(s): 4.17+

Issue: https://issues.redhat.com/browse/OSDOCS-12142

Link to docs preview: https://84179--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hosted_control_planes/hcp_high_availability/hcp-backup-restore-virt.html

QE review:

  • QE has approved this change.

Additional information: To be merged on Nov. 6 in alignment with the MCE 2.7 release.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 28, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 28, 2024

@lahinson lahinson force-pushed the osdocs-12142-backup-restore-hcp-kubevirt branch from aba4729 to d9fc3ff Compare October 29, 2024 13:54
Copy link

@davidvossel davidvossel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 29, 2024
@nunnatsa
Copy link
Contributor

nunnatsa commented Nov 3, 2024

Thanks @lahinson !

/lgtm

@lahinson lahinson added peer-review-needed Signifies that the peer review team needs to review this PR branch/enterprise-4.17 branch/enterprise-4.18 labels Nov 4, 2024
@jeana-redhat jeana-redhat added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Nov 4, 2024
Copy link
Contributor

@jeana-redhat jeana-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really nice! Most of my comments are just things to consider.

/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done

----
+
<1> This field starts the recovery of pods with the included persistent volumes.
<2> By setting `existingResourcePolicy` to `update` ensures that any objects are overwritten with backup content. This action can cause issues with objects that contain immutable fields, which is why you deleted the `HostedCluster`, node pools, and PVCs. If you do not set this policy, the Velero engine skips the restoration of objects that already exist.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<2> By setting `existingResourcePolicy` to `update` ensures that any objects are overwritten with backup content. This action can cause issues with objects that contain immutable fields, which is why you deleted the `HostedCluster`, node pools, and PVCs. If you do not set this policy, the Velero engine skips the restoration of objects that already exist.
<2> Setting `existingResourcePolicy` to `update` ensures that any existing objects are overwritten with backup content. This action can cause issues with objects that contain immutable fields, which is why you deleted the `HostedCluster`, node pools, and PVCs. If you do not set this policy, the Velero engine skips the restoration of objects that already exist.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the option of skipping this is mentioned, are there any consequences or considerations that should be covered? If you don't set the policy, did you need to delete the objects at the start?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nunnatsa Jeana has another good question here. Can you answer it?

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Nov 4, 2024
@lahinson lahinson force-pushed the osdocs-12142-backup-restore-hcp-kubevirt branch from d9fc3ff to c6bc0e2 Compare November 4, 2024 19:59
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 4, 2024
@openshift-ci
Copy link

openshift-ci bot commented Nov 4, 2024

New changes are detected. LGTM label has been removed.

@lahinson lahinson force-pushed the osdocs-12142-backup-restore-hcp-kubevirt branch from c6bc0e2 to ed92fd1 Compare November 5, 2024 14:00
@openshift-ci
Copy link

openshift-ci bot commented Nov 5, 2024

@lahinson: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions 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.

@lahinson lahinson merged commit 59b7b40 into openshift:main Nov 6, 2024
@lahinson
Copy link
Contributor Author

lahinson commented Nov 6, 2024

/cherrypick enterprise-4.18

@lahinson
Copy link
Contributor Author

lahinson commented Nov 6, 2024

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@lahinson: new pull request created: #84535

Details

In response to this:

/cherrypick enterprise-4.18

Instructions 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.

@openshift-cherrypick-robot

@lahinson: new pull request created: #84536

Details

In response to this:

/cherrypick enterprise-4.17

Instructions 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.17 branch/enterprise-4.18 peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants