×

You can install OKD on Amazon Web Services using installer-provisioned, user-provisioned infrastructure, or on a single node, depending on the needs of your use case.

The default installation type uses installer-provisioned infrastructure, where the installation program provisions the underlying infrastructure for the cluster.

You can also install OKD on infrastructure that you provision. If you do not use infrastructure that the installation program provisions, you must manage and maintain the cluster resources yourself.

You can also install OKD on a single node, which is a specialized installation method that is ideal for edge computing environments.

Installing a cluster on installer-provisioned infrastructure

You can install a cluster on AWS infrastructure that is provisioned by the OKD installation program, by using one of the following methods:

You can install OKD on AWS infrastructure that is provisioned by the OKD installation program. You can install a cluster quickly by using the default configuration options.

You can install a customized cluster on AWS infrastructure that the installation program provisions. You can also customize your OKD network configuration during installation, so that your cluster can coexist with your existing IP address allocations and adhere to your network requirements. The installation program allows for some customization to be applied at the installation stage. Many other customization options are available post-installation.

You can install OKD on AWS on installer-provisioned infrastructure by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components.

You can install OKD on an existing AWS Virtual Private Cloud (VPC). You can use this installation method if you have constraints set by the guidelines of your company, such as limits when creating new accounts or infrastructure.

You can install a private cluster on an existing AWS VPC. You can use this method to deploy OKD on an internal network that is not visible to the internet.

OKD can be deployed into AWS regions that are specifically designed for US government agencies at the federal, state, and local level, as well as contractors, educational institutions, and other US customers that must run sensitive workloads in the cloud.

Installing a cluster on user-provisioned infrastructure

You can install a cluster on AWS in one of two ways: on infrastructure that you provide or infrastructure that you provide by using an internal mirror of the installation release content.

To install OKD on AWS infrastructure that you provide, you can use the provided CloudFormation templates to create stacks of AWS resources that represent each of the components required for an OKD installation.

To install a cluster that does not require an active internet connection to obtain the software components, install OKD on AWS infrastructure that you provide by using an internal mirror of the installation release content. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content. While you can install OKD by using the mirrored content, your cluster still requires internet access to use the AWS APIs.

Installing a cluster on a single node

Installing OKD on a single node alleviates some of the requirements for high availability and large scale clusters. However, you must address requirements for installing on a single node, and the additional requirements for installing single-node OpenShift on a cloud provider.

After addressing the requirements for single node installation, use the installing a customized cluster on AWS procedure to install the cluster. The installing single-node OpenShift manually section contains an exemplary install-config.yaml file when installing an OKD cluster on a single node.