openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Improving ROSA disaster recovery and cluster state backup info

Browse Source
This commit is contained in:
Elizabeth Hartman
2024-07-09 17:29:47 -04:00
committed by openshift-cherrypick-robot
parent 560f2f3cce
commit 473cbc7583
1 changed files with 55 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

105
modules/rosa-sdpolicy-platform.adoc
View File

@@ -21,56 +21,6 @@ ifndef::rosa-with-hcp[]
{product-title} (ROSA) platform.
endif::rosa-with-hcp[]
[id="rosa-sdpolicy-backup-policy_{context}"]
== Cluster backup policy
[IMPORTANT]
====
Red{nbsp}Hat does not provide a backup method for ROSA clusters with STS, which is the default. It is critical that customers have a backup plan for their applications and application data.
ifndef::rosa-with-hcp[]
The table below only applies to clusters created with IAM user credentials.
endif::rosa-with-hcp[]
====
Application and application data backups are not a part of the
ifdef::rosa-with-hcp[]
{hcp-title-first} service.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title} service.
The following table outlines the cluster backup policy.
//Verify if the corresponding tables in policy-incident.adoc and rosa-policy-incident.adoc also need to be updated.
[cols= "3a,2a,2a,3a",options="header"]
|===
|Component
|Snapshot frequency
|Retention
|Notes
.2+|Full object store backup
|Daily
|7 days
.2+|This is a full backup of all Kubernetes objects like etcd. No persistent volumes (PVs) are backed up in this backup schedule.
|Weekly
|30 days
|Full object store backup
|Hourly
|24 hour
|This is a full backup of all Kubernetes objects like etcd. No PVs are backed up in this backup schedule.
|Node root volume
|Never
|N/A
|Nodes are considered to be short-term. Nothing critical should be stored on a node's root volume.
|===
endif::rosa-with-hcp[]
[id="rosa-sdpolicy-autoscaling_{context}"]
== Autoscaling
Node autoscaling is available on
@@ -125,6 +75,61 @@ ifndef::rosa-with-hcp[]
endif::rosa-with-hcp[]
clusters at this time. However, custom labels are supported when creating new machine pools.
[id="rosa-sdpolicy-backup-policy_{context}"]
== Cluster backup policy
[IMPORTANT]
====
Red Hat does not provide a backup method for ROSA clusters with STS. It is critical that customers have a backup plan for their applications and application data.
====
Application and application data backups are not a part of the
ifdef::rosa-with-hcp[]
{hcp-title-first} service.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title} service.
ifndef::rosa-with-hcp[]
[%collapsible]
====
The table below only applies to non-STS clusters. The following components are used by Red Hat in extenuating circumstances.
//Verify if the corresponding tables in policy-incident.adoc and rosa-policy-incident.adoc also need to be updated.
[cols= "3a,2a,2a,3a",options="header"]
|===
|Component
|Snapshot frequency
|Retention
|Notes
.2+|Full object store backup
|Daily
|7 days
.2+|This is a full backup of all Kubernetes objects like etcd. No persistent volumes (PVs) are backed up in this backup schedule.
|Weekly
|30 days
|Full object store backup
|Hourly
|24 hour
|This is a full backup of all Kubernetes objects like etcd. No PVs are backed up in this backup schedule.
|Node root volume
|Never
|N/A
|Nodes are considered to be short-term. Nothing critical should be stored on a node's root volume.
|===
endif::rosa-with-hcp[]
====
endif::rosa-with-hcp[]
[id="rosa-sdpolicy-openshift-version_{context}"]
== OpenShift version
ifdef::rosa-with-hcp[]