Deployment options - Red Hat OpenShift Service on AWS
Differences between ROSA with HCP and ROSA classic

Deployment options

ROSA provides two cluster deployment models: ROSA with hosted control planes (ROSA with HCP) and ROSA classic. With ROSA with HCP, each cluster has a dedicated control plane that is isolated within Red Hat’s AWS account and managed by Red Hat. With ROSA classic, cluster control plane infrastructure is hosted in the customer’s AWS account.

ROSA with HCP offers a more efficient control plane architecture that helps reduces the AWS infrastructure fees incurred when running ROSA and allows for faster cluster creation times. Both cluster deployment models can be enabled in the AWS ROSA console. You have the choice to select which deployment model you want to use when you provision ROSA clusters using the ROSA CLI.

Note

ROSA with hosted control planes does not offer compliance certifications or Federal Information Processing Standards (FIPS) at this time. For more information, see Compliance in the Red Hat documentation.

Differences between ROSA with HCP and ROSA classic

There are several technical differences between ROSA with HCP and ROSA classic.

ROSA with HCP ROSA classic

Cluster infrastructure hosting

  • Control plane components, such as etcd, API server, and oauth, are hosted on Red Hat-owned and managed AWS accounts. Worker node infrastructure is hosted on the customer’s AWS account. Does not use dedicated infrastructure nodes; platform components are deployed to worker nodes.

  • Control plane components are hosted on the customer’s AWS account, alongside infrastructure and worker nodes.

Provisioning time

  • Approximately 10 minutes.

  • Approximately 40 minutes.

Architecture

  • Control plane infrastructure is fully managed by Red Hat. Control plane infrastructure is not directly available to end customers, except through dedicated and explicitly exposed endpoints.

  • Worker nodes are hosted on the customer’s AWS account.

  • Control plane infrastructure is hosted in the customer’s AWS account.

  • Worker nodes are hosted on the customer’s AWS account.

AWS Identity and Access Management

  • Uses AWS managed policies.

  • Uses customer managed policies that are defined by the service.

Minimum Amazon EC2 footprint

  • One cluster requires a minimum of two nodes hosted on the customer’s AWS account.

  • One cluster requires a minimum of seven nodes hosted on the customer’s AWS account.

Cluster provisioning

  • Provision clusters using the ROSA CLI.

  • Customers provision clusters that deploy the control plane components into Red Hat’s AWS account.

  • Customers provision machine pools that deploy worker nodes into the customer’s AWS account.

  • Provision clusters using the ROSA CLI or web UI.

  • Cluster control plane, worker nodes, and infrastructure nodes are provisioned into the customer’s AWS account.

Upgrades

  • Upgrade control plane and machine pools separately.

  • Entire cluster must be upgraded at the same time.

AWS Regions

Compliance

  • For compliance information, see Compliance in the Red Hat documentation.

  • For compliance information, see Compliance in the Red Hat documentation.