| title | slug | description | keywords | page_purpose | audience | author | content_owner | sort_order |
|---|---|---|---|---|---|---|---|---|
Hosting tiers table |
hosting-tiers-table |
Describes the differences between OCP clusters |
ocp clusters, hosting tiers, product tools, clusters |
Provide clear content regarding private cloud hosting tiers |
technical lead, developer |
Steven Barre, Billy Li, Nick Corcoran |
Olena Mitovska |
6 |
Last updated: February 29, 2024
This section presents a concise summary table highlighting key distinctions among OCP editions. These differentiators encompass target uptime (availability), maximum data sensitivity, integrated high availability (HA), disaster recovery (DR) options, release plan details, supported operators, scalability limits, and interoperability with other hosting services.
The aim is to provide a clear and easily understandable overview of each OCP edition's unique attributes.
| Silver hosting tier | Details |
|---|---|
| OCP | Silver |
| Target up time (availability) | Platform availability for the Silver hosting tier is 90% for single-node and 99.5% for multi-node deployments |
| Maximum data sensitivity | - Protected B: Stored at rest (in a database or file storage) - Protected C: Processing only (must be stored elsewhere) |
| Integrated HA, DR options | TransportServerClaims |
| Underlying release plan | Aim for N minus 1 tracking Red Hat point releases for OpenShift |
| Slate of supported operators | - Horizontal Pod Autoscaler - Vertical Pod Autoscaler - Custom Metrics Autoscaler - Pipelines: Tekton - CrunchyDB - ArgoCD - Kyverno - License required Red Hat integration - Enterprise DB - JBoss EAP |
| Upper limit of scalability | - 1500 CPU Cores - 30TB Storage - 10G Networking |
| Options for security interoperability with other hosting services | - Shared Egress IP for the cluster can be used in firewall rules with STMS-Classic - Cluster can directly egress to the public internet - Public internet can connect to cluster API and hosted apps |
| Gold hosting tier | Details |
|---|---|
| OCP | Gold |
| Target up time (availability) | Platform availability for the Gold hosting tier is 99.95%, specifically for applications with multi-node deployments that have a geographic failover to the Gold DR cluster in the Calgary data centre, minimizing disruption. Without DR, Gold maintains the same availability as Silver |
| Maximum data sensitivity | - Protected B: Stored at rest (in a database or file storage) - Protected C: Processing only (must be stored elsewhere) |
| Integrated HA, DR options | - TransportServerClaims to connect between Gold and Gold DR -Global Load Balancing between clusters for Active/Passive DR |
| Underlying release plan | Aim for N minus 1 tracking Red Hat point releases for OpenShift |
| Slate of supported operators | - Horizontal Pod Autoscaler - Vertical Pod Autoscaler - Custom Metrics Autoscaler - Pipelines: Tekton - CrunchyDB - ArgoCD - Kyverno - License required Red Hat integration - Enterprise DB - JBoss EAP |
| Upper limit of scalability | - 225 CPU Cores - 16TB Storage - 10G Networking |
| Options for security interoperability with other hosting services | - Shared Egress IP for the cluster can be used in firewall rules with STMS-Classic - Cluster can directly egress to the public internet - Public internet can connect to cluster API and hosted apps |
| Emerald hosting tier | Details |
|---|---|
| OCP | Emerald |
| Target up time (availability) | Platform availability for the Emerald hosting tier is 90% for single-node application deployments and 99.5% for multi-node deployments |
| Maximum data sensitivity | Protected C - Storage and/or processing |
| Integrated HA, DR options | None |
| Underlying release plan | - Extended Update Support (EUS) - Only updates to even numbered releases of OpenShift |
| Slate of supported operators | - Horizontal Pod Autoscaler - Vertical Pod Autoscaler - Custom Metrics Autoscaler - Pipelines: Tekton - CrunchyDB - ArgoCD - Kyverno - License required Red Hat integration - Enterprise DB - JBoss EAP - IMB MQ |
| Upper limit of scalability | - 175 CPU Cores - 16TB Storage - 10G Networking |
| Options for security interoperability with other hosting services | - Per Namespace Egress subnet can be used in firewall rules with STMS-Classic - Only access for some workloads to the public internet and only via a proxy server - API is only available inside SPANBC - Hosted apps may be granted access from the public internet - Access to VM-SDN workloads |