This is a cache of https://docs.openshift.com/rosa/rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.html. It is a snapshot of the page at 2024-11-19T03:05:17.631+0000.
Creating an AWS PrivateLink cluster on ROSA | Install ROSA Classic clusters | Red Hat OpenShift Service on AWS
  1. Documentation
    2. history bug_report picture_as_pdf
×

Creating an AWS PrivateLink cluster on ROSA

edit

This document describes how to create a ROSA cluster using AWS PrivateLink.

edit

A Red Hat OpenShift Service on AWS cluster can be created without any requirements on public subnets, internet gateways, or network address translation (NAT) gateways. In this configuration, Red Hat uses AWS PrivateLink to manage and monitor a cluster to avoid all public ingress network traffic. Without a public subnet, it is not possible to configure an application router as public. Configuring private application routers is the only option.

For more information, see AWS PrivateLink on the AWS website.

You can only make a PrivateLink cluster at installation time. You cannot change a cluster to PrivateLink after installation.
edit

For AWS PrivateLink clusters, internet gateways, NAT gateways, and public subnets are not required, but the private subnets must have internet connectivity provided to install required components. At least one single private subnet is required for Single-AZ clusters and at least 3 private subnets are required for Multi-AZ clusters. The following table shows the AWS resources that are required for a successful installation:

Table 1. Required AWS resources
Component AWS Type Description

VPC

  • AWS::EC2::VPC

  • AWS::EC2::VPCEndpoint

You must provide a VPC for the cluster to use.

Network access control

  • AWS::EC2::NetworkAcl

  • AWS::EC2::NetworkAclEntry

You must allow access to the following ports:

Port Reason

80

Inbound HTTP traffic

443

Inbound HTTPS traffic

22

Inbound SSH traffic

1024-65535

Inbound ephemeral traffic

0-65535

Outbound ephemeral traffic

Private subnets

  • AWS::EC2::Subnet

  • AWS::EC2::RouteTable

  • AWS::EC2::SubnetRouteTableAssociation

Your VPC must have private subnets in 1 availability zone for Single-AZ deployments or 3 availability zones for Multi-AZ deployments. You must provide appropriate routes and route tables.
edit

You can create an AWS PrivateLink cluster using the Red Hat OpenShift Service on AWS (ROSA) CLI, rosa.

AWS PrivateLink is supported on existing VPCs only.
Prerequisites

  • You have available AWS service quotas.

  • You have enabled the ROSA service in the AWS Console.

  • You have installed and configured the latest Red Hat OpenShift Service on AWS (ROSA) CLI, rosa, on your installation host.

Procedure

Creating a cluster can take up to 40 minutes.

  1. With AWS PrivateLink, you can create a cluster with a single availability zone (Single-AZ) or multiple availability zones (Multi-AZ). In either case, your machine’s classless inter-domain routing (CIDR) must match your virtual private cloud’s CIDR. See Requirements for using your own VPC and VPC Validation for more information.

    If you use a firewall, you must configure it so that Red Hat OpenShift Service on AWS can access the sites that it requires to function.

    For more information, see the AWS PrivateLink firewall prerequisites section.

    If your cluster name is longer than 15 characters, it will contain an autogenerated domain prefix as a sub-domain for your provisioned cluster on *.openshiftapps.com.

    To customize the subdomain, use the --domain-prefix flag. The domain prefix cannot be longer than 15 characters, must be unique, and cannot be changed after cluster creation.

    • To create a Single-AZ cluster:

      $ rosa create cluster --private-link --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id>

    • To create a Multi-AZ cluster:

      $ rosa create cluster --private-link --multi-az --cluster-name=<cluster-name> [--machine-cidr=<VPC CIDR>/16] --subnet-ids=<private-subnet-id1>,<private-subnet-id2>,<private-subnet-id3>

  2. Enter the following command to check the status of your cluster. During cluster creation, the State field from the output will transition from pending to installing, and finally to ready.

    $ rosa describe cluster --cluster=<cluster_name>

    If installation fails or the State field does not change to ready after 40 minutes, check the installation troubleshooting documentation for more details.

  3. Enter the following command to follow the OpenShift installer logs to track the progress of your cluster:

    $ rosa logs install --cluster=<cluster_name> --watch
edit

With AWS PrivateLink clusters, a public hosted zone and a private hosted zone are created in Route 53. With the private hosted zone, records within the zone are resolvable only from within the VPC to which it is assigned.

The Let’s Encrypt dns-01 validation requires a public zone so that valid, publicly trusted certificates can be issued for the domain. The validation records are deleted after Let’s Encrypt validation is complete; however, the zone is still required for issuing and renewing these certificates, which are typically required every 60 days. While these zones usually appear empty, it is serving a critical role in the validation process.

For more information about private hosted zones, see AWS private hosted zones documentation. For more information about public hosted zones, see AWS public hosted zones documentation.

Prerequisites

  • Your corporate network or other VPC has connectivity

  • UDP port 53 and TCP port 53 ARE enabled across your networks to allow for dns queries

  • You have created an AWS PrivateLink cluster using Red Hat OpenShift Service on AWS

Procedure

  1. To allow for records such as api.<cluster_domain> and *.apps.<cluster_domain> to resolve outside of the VPC, configure a Route 53 Resolver Inbound Endpoint.

  2. When you configure the inbound endpoint, select the VPC and private subnets that were used when you created the cluster.

  3. After the endpoints are operational and associated, configure your corporate network to forward dns queries to those IP addresses for the top-level cluster domain, such as drow-pl-01.htno.p1.openshiftapps.com.

  4. If you are forwarding dns queries from one VPC to another VPC, configure forwarding rules.

  5. If you are configuring your remote network dns server, see your specific dns server documentation to configure selective dns forwarding for the installed cluster domain.

edit

Next steps

Additional resources