Skip to content

Commit 5d2511a

Browse files
authored
Merge pull request #109614 from lahinson/ocpbugs-80926-fix-title-shortdesc
[OCPBUGS-80926]: Correcting text in on-premise backup procedure for HCP
2 parents f36a984 + a82aa12 commit 5d2511a

2 files changed

Lines changed: 6 additions & 5 deletions

File tree

hosted_control_planes/hcp_high_availability/hcp-backup-restore-on-premise.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
You can back up and restore etcd on a hosted cluster in an on-premise environment to fix failures.
9+
You can back up and restore etcd for {hcp} in an on-premise environment to fix failures.
1010

1111
include::modules/hosted-cluster-etcd-backup-restore-on-premise.adoc[leveloffset=+1]
1212

modules/hosted-cluster-etcd-backup-restore-on-premise.adoc

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,7 @@
77
= Backing up and restoring etcd on a hosted cluster in an on-premise environment
88

99
[role="_abstract"]
10-
By backing up and restoring etcd on a hosted cluster, you can fix failures, such as corrupted or missing data in an etcd member of a three node cluster. If multiple members of the etcd cluster encounter data loss or have a `CrashLoopBackOff` status, this approach helps prevent an etcd quorum loss.
11-
12-
:FeatureName: Restoring etcd on a hosted cluster in an on-premise environment
13-
include::snippets/technology-preview.adoc[]
10+
By backing up and restoring etcd on a hosted cluster, you can fix failures, such as corrupted or missing data in an etcd member of a three-node cluster. If members of the etcd cluster lose data or have a `CrashLoopBackOff` status, this approach helps prevent an etcd quorum loss.
1411

1512
.Prerequisites
1613

@@ -27,6 +24,10 @@ include::snippets/technology-preview.adoc[]
2724
* Hosted cluster service publishing strategy prerequisites:
2825
+
2926
** When you restore a hosted cluster to a different management cluster, all services in the hosted cluster must be configured with a fixed hostname in its `servicePublishingStrategy` property. This requirement applies to all platforms: {aws-short}, Agent, {VirtProductName}, and {rh-openstack-first}.
27+
+
28+
:FeatureName: Restoring a hosted cluster to a different management cluster
29+
include::snippets/technology-preview.adoc[]
30+
+
3031
** The `APIServer` service must have a fixed hostname. Otherwise, the restore process fails and nodes cannot rejoin the cluster. For {hcp} on {aws-short}, the `APIServer` service can also use a `Route` service publishing strategy with a fixed hostname.
3132
** For production environments, it is strongly recommended to configure all services with fixed hostnames. By having fixed hostnames, you can ensure full service continuity and DNS consistency during the restore process on a different management cluster.
3233

0 commit comments

Comments
 (0)