Procedure

1. Log in to your AWS account. If necessary, you can create a new AWS account by following the Content from aws.amazon.com is not included.AWS documentation.

2. Create an IAM user with STS:AllowAssumeRole permissions within the AWS account.

   1. Open the Content from console.aws.amazon.com is not included.IAM dashboard of the AWS Management Console.
   2. In the Policies section, click Create Policy.

   3. Select the JSON tab and replace the existing text with the following:

      {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": "sts:AssumeRole",
                "Resource": "*"
            }
        ]
      }

      Copy code to clipboard
   4. Click Next:Tags.
   5. Optional: Add tags. Click Next:Review
   6. Provide an appropriate name and description, then click Create Policy.
   7. In the Users section, click Add user.
   8. Provide an appropriate user name.
   9. Select AWS Management Console access as the AWS access type.
   10. Adjust the password requirements as necessary for your organization, then click Next:Permissions.

   11. Click the Attach existing policies directly option. Search for and check the policy created in previous steps.

       Note

       It is not recommended to set a permissions boundary.

   12. Click Next: Tags, then click Next: Review. Confirm the configuration is correct.
   13. Click Create user, a success page appears.
   14. Gather the IAM user’s Amazon Resource Name (ARN). The ARN has the following format: arn:aws:iam::000111222333:user/username. Click Close.
3. Open This content is not included.OpenShift Cluster Manager in your browser and select the cluster you want to allow AWS infrastructure access.
4. Select the Access control tab, and scroll to the AWS Infrastructure Access section.
5. Paste the AWS IAM ARN and select Network Management or Read-only permissions, then click Grant role.
6. Copy the AWS OSD console URL to your clipboard.
7. Sign in to your AWS account with your Account ID or alias, IAM user name, and password.
8. In a new browser tab, paste the AWS OSD Console URL that routes to the AWS Switch Role page.
9. Your account number and role are filled in already. Choose a display name if necessary, then click Switch Role.

Procedure

1. Content from docs.aws.amazon.com is not included.Initiate the VPC peering request.
2. Content from docs.aws.amazon.com is not included.Accept the VPC peering request.
3. Content from docs.aws.amazon.com is not included.Update your Route tables for the VPC peering connection.

Procedure

1. Content from docs.aws.amazon.com is not included.Create a customer gateway to configure the VPN connection.
2. If you do not already have a Virtual Private Gateway attached to the intended VPC, Content from docs.aws.amazon.com is not included.create and attach a Virtual Private Gateway.
3. Content from docs.aws.amazon.com is not included.Configure routing and enable VPN route propagation.
4. Content from docs.aws.amazon.com is not included.Update your security group.

5. Content from docs.aws.amazon.com is not included.Establish the Site-to-Site VPN connection.

   Note

   Note the VPC subnet information, which you must add to your configuration as the remote network.

Procedure

1. Content from docs.aws.amazon.com is not included.Create a VIF or Content from docs.aws.amazon.com is not included.view your existing VIFs to determine the type of direct connection you need to create.

2. Create your gateway.

   1. If the Direct Connect VIF type is Private, Content from docs.aws.amazon.com is not included.create a virtual private gateway.
   2. If the Direct Connect VIF is Public, Content from docs.aws.amazon.com is not included.create a Direct Connect gateway.

3. If you have an existing gateway you want to use, Content from docs.aws.amazon.com is not included.create an association proposal and send the proposal to the DXGateway owner for approval.

   Warning

   When connecting to an existing DXGateway, you are responsible for the Content from aws.amazon.com is not included.costs.

Procedure

1. Log in to This content is not included.OpenShift Cluster Manager.
2. Click Create cluster → OpenShift Dedicated → Create cluster.
3. Configure your cluster details.
4. When selecting your preferred network configuration, select Advanced.

5. Select Private.

   Warning

   When set to Private, you cannot access your cluster unless you have configured the private connections in your cloud provider as outlined in the prerequisites.

6. Click Create cluster. The cluster creation process begins and takes about 30-40 minutes to complete.

Procedure

1. Log in to This content is not included.OpenShift Cluster Manager.
2. Select the public cluster you want to make private.

3. On the Networking tab, select Make API private under Control Plane API endpoint.

   Warning

   When set to Private, you cannot access your cluster unless you have configured the private connections in your cloud provider as outlined in the prerequisites.

4. Click Change settings.

   Note

   Transitioning your cluster between private and public can take several minutes to complete.

Procedure

1. Log in to This content is not included.OpenShift Cluster Manager.
2. Select the private cluster you want to make public.
3. On the Networking tab, deselect Make API private under Control Plane API endpoint.

4. Click Change settings.

   Note

   Transitioning your cluster between private and public can take several minutes to complete.

Procedure

1. Navigate to This content is not included.OpenShift Cluster Manager and select your cluster.
2. Under the Machine pools tab, click Add machine pool.
3. Add a Machine pool name.

4. Select a Compute node instance type from the list. The instance type defines the vCPU and memory allocation for each compute node in the machine pool.

   Note

   You cannot change the instance type for a machine pool after the pool is created.

5. Configure the node count by choosing one of the following options:

   • Enable autoscaling: Select Enable autoscaling to automatically scale the number of machines in your machine pool to meet the deployment needs. Set the minimum and maximum node count limits for autoscaling. The cluster autoscaler does not reduce or increase the machine pool node count beyond the limits that you specify.

     Note

     The Enable autoscaling option is only available for OpenShift Dedicated if you have the capability.cluster.autoscale_clusters subscription. For more information, contact your sales representative or Red Hat support.

     • If you deployed your cluster using a single availability zone, set the Minimum and maximum node count. This defines the minimum and maximum compute node limits in the availability zone.
     • If you deployed your cluster using multiple availability zones, set the Minimum nodes per zone and Maximum nodes per zone. This defines the minimum and maximum compute node limits per zone.

   • Manual node count: If you do not enable autoscaling, select a compute node count:

     • If you deployed your cluster using a single availability zone, select a Compute node count from the drop-down menu. This defines the number of compute nodes to provision to the machine pool for the zone.
     • If you deployed your cluster using multiple availability zones, select a Compute node count (per zone) from the drop-down menu. This defines the number of compute nodes to provision to the machine pool per zone.

6. Optional: Configure advanced machine pool settings by expanding the appropriate sections and providing values:

   1. For Node labels and taints, expand the Edit node labels and taints menu.
   2. Under Node labels, add Key and Value entries for your node labels.

   3. Under Taints, add Key and Value entries for your taints. For each taint, select an Effect from the drop-down menu. Available options include NoSchedule, PreferNoSchedule, and NoExecute.

      Note

      Creating a machine pool with taints is only possible if the cluster already has at least one machine pool without a taint. Alternatively, you can add node labels and taints after you create the machine pool.

      • Custom security groups: Select additional custom security groups to use for nodes in this machine pool. You must have already created the security groups and associated them with the VPC that you selected for this cluster. You cannot add or edit security groups after you create the machine pool. For more information, see the requirements for security groups in the "Additional resources" section.
      • Amazon EC2 Spot Instances: If you deployed OpenShift Dedicated on AWS using the Customer Cloud Subscription (CCS) model and want to configure your machine pool to deploy machines as non-guaranteed AWS Spot Instances, select Use Amazon EC2 Spot Instances. Leave Use On-Demand instance price selected to use the on-demand instance price, or select Set maximum price to define a maximum hourly price for a Spot Instance. For more information about Amazon EC2 Spot Instances, see the Content from aws.amazon.com is not included.AWS documentation.
7. Click Add machine pool to create the machine pool.

Procedure

1. From This content is not included.OpenShift Cluster Manager, navigate to the Cluster List page and select the cluster that contains the machine pool that you want to delete.
2. On the selected cluster, select the Machine pools tab.
3. Under the Machine pools tab, click the Options menu for the machine pool that you want to delete.
4. Click Delete.

Procedure

1. Navigate to This content is not included.OpenShift Cluster Manager and select your cluster.
2. Under the Machine pools tab, click the Options menu for the machine pool that you want to scale.
3. Select Scale.

4. Specify the node count:

   • If you deployed your cluster using a single availability zone, specify the Node count in the drop-down menu.

   • If you deployed your cluster using multiple availability zones, specify the Node count per zone in the drop-down menu.

     Note

     Your subscription determines the number of nodes that you can select.

5. Click Apply to scale the machine pool.

Procedure

1. Navigate to This content is not included.OpenShift Cluster Manager and select your cluster.
2. Under the Machine pools tab, click the Options menu for the machine pool that you want to add a taint to.
3. Select Edit taints.
4. Add Key and Value entries for your taint.
5. Select an Effect for your taint from the list. Available options include NoSchedule, PreferNoSchedule, and NoExecute.
6. Select Add taint if you want to add more taints to the machine pool.
7. Click Save to apply the taints to the machine pool.

Verification

1. Under the Machine pools tab, select > next to your machine pool to expand the view.
2. Verify that your taints are listed under Taints in the expanded view.

Procedure

1. From This content is not included.OpenShift Cluster Manager, navigate to the Cluster List page and select the cluster that you want to enable autoscaling for.
2. On the selected cluster, select the Machine pools tab.
3. Click the Options menu at the end of the machine pool that you want to enable autoscaling for and select Edit.
4. On the Edit machine pool dialog, select the Enable autoscaling checkbox.
5. Select Save to save these changes and enable autoscaling for the machine pool.

Procedure

1. From This content is not included.OpenShift Cluster Manager, navigate to the Cluster List page and select the cluster with autoscaling that must be disabled.
2. On the selected cluster, select the Machine pools tab.
3. Click the Options menu at the end of the machine pool with autoscaling and select Edit.
4. On the Edit machine pool dialog, clear the Enable autoscaling checkbox.
5. Select Save to save these changes and disable autoscaling from the machine pool.