openshift-docs/modules/rosa-sdpolicy-platform.adoc

// Module included in the following assemblies:
//
// * rosa_architecture/rosa_policy_service_definition/rosa-service-definition.adoc
// * rosa_architecture/rosa_policy_service_definition/rosa-hcp-service-definition.adoc

ifeval::["{context}" == "rosa-hcp-service-definition"]
:rosa-with-hcp:
endif::[]

:_mod-docs-content-type: ASSEMBLY
[id="rosa-sdpolicy-platform_{context}"]
= Platform
:productwinc: Red{nbsp}Hat OpenShift support for Windows Containers

This section provides information about the service definition for the
ifdef::rosa-with-hcp[]
{hcp-title-first} platform.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title} (ROSA) platform.
endif::rosa-with-hcp[]

[id="rosa-sdpolicy-autoscaling_{context}"]
== Autoscaling
Node autoscaling is available on
ifdef::rosa-with-hcp[]
{hcp-title-first}.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}.
endif::rosa-with-hcp[]
You can configure the autoscaler option to automatically scale the number of machines in a cluster.

[id="rosa-sdpolicy-daemonsets_{context}"]
== Daemonsets
Customers can create and run daemonsets on
ifdef::rosa-with-hcp[]
{hcp-title-first}.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}. To restrict daemonsets to only running on worker nodes, use the following `nodeSelector`:
[source,yaml]
----
...
spec:
  nodeSelector:
    role: worker
...
----
endif::rosa-with-hcp[]

[id="rosa-sdpolicy-multiple-availability-zone_{context}"]
== Multiple availability zone

ifdef::rosa-with-hcp[]
Control plane components are always deployed across multiple availability zones, regardless of a customer's worker node configuration.
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
In a multiple availability zone cluster, control plane nodes are distributed across availability zones and at least one worker node is required in each availability zone.
endif::rosa-with-hcp[]

[id="rosa-sdpolicy-node-labels_{context}"]
== Node labels
Custom node labels are created by Red{nbsp}Hat during node creation and cannot be changed on
ifdef::rosa-with-hcp[]
{hcp-title-first}
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}
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[]
{hcp-title-first}
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}
endif::rosa-with-hcp[]
is run as a service and is kept up to date with the latest OpenShift Container Platform version. Upgrade scheduling to the latest version is available.

[id="rosa-sdpolicy-upgrades_{context}"]
== Upgrades
Upgrades can be scheduled using the ROSA CLI, `rosa`, or through {cluster-manager}.

See the link:https://docs.openshift.com/rosa/rosa_policy/rosa-life-cycle.html[{product-title} Life Cycle] for more information on the upgrade policy and procedures.

[id="rosa-sdpolicy-window-containers_{context}"]
== Windows Containers
{productwinc} is not available on {product-title} at this time.

[id="rosa-sdpolicy-container-engine_{context}"]
== Container engine
ifdef::rosa-with-hcp[]
{hcp-title-first}
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}
endif::rosa-with-hcp[]
runs on OpenShift 4 and uses link:https://www.redhat.com/en/blog/red-hat-openshift-container-platform-4-now-defaults-cri-o-underlying-container-engine[CRI-O] as the only available container engine.

[id="rosa-sdpolicy-operating-system_{context}"]
== Operating system
ifdef::rosa-with-hcp[]
{hcp-title-first}
endif::rosa-with-hcp[]
ifndef::rosa-with-hcp[]
{product-title}
endif::rosa-with-hcp[]
runs on OpenShift 4 and uses Red{nbsp}Hat CoreOS as the operating system for all control plane and worker nodes.

[id="rosa-sdpolicy-red-hat-operator_{context}"]
== Red{nbsp}Hat Operator support
Red{nbsp}Hat workloads typically refer to Red{nbsp}Hat-provided Operators made available through Operator Hub. Red{nbsp}Hat workloads are not managed by the Red{nbsp}Hat SRE team, and must be deployed on worker nodes. These Operators may require additional Red{nbsp}Hat subscriptions, and may incur additional cloud infrastructure costs. Examples of these Red{nbsp}Hat-provided Operators are:

* {rhq-short}
* Red{nbsp}Hat Advanced Cluster Management
* Red{nbsp}Hat Advanced Cluster Security
* {SMProductName}
* {ServerlessProductName}
* {logging-sd}
* {pipelines-title}

[id="rosa-sdpolicy-kubernetes-operator_{context}"]
== Kubernetes Operator support
All Operators listed in the OperatorHub marketplace should be available for installation. These Operators are considered customer workloads, and are not monitored by Red{nbsp}Hat SRE.

ifeval::["{context}" == "rosa-hcp-service-definition"]
:!rosa-with-hcp:
endif::[]