Reference Architecture Summary
The deployment of Red Hat OpenShift Container Platform varies among several factors that impact the installation process. Key considerations include:
- Which installation method do you want to use?
- How many instances do you require in the cluster?
- Is high availability required?
- Which installation type do you want to use: RPM or containerized?
- Is my installation supported if integrating with other Red Hat technologies?
For more information regarding the different options in installing an Red Hat OpenShift Container Platform cluster visit: Red Hat OpenShift Container Platform Chapter 2. Installing a Cluster
The initial planning process for this reference architecture answers these questions for this environment as follows:
- Which installation method do you want to use? Advanced Installation
- How many instances do you require in the cluster? 10
- Is high availability required? Yes
- Which installation type do you want to use: RPM or containerized? RPM
- Is my installation supported if integrating with other Red Hat technologies? Yes
A pictorial representation of the environment in this reference environment is shown below.
The Red Hat OpenShift Container Platform Architecture diagram shows the different components in the reference architecture.
- The Red Hat OpenShift Container Platform instances:
- Bastion instance
- Three master instances
- Three infrastructure instances
- Three application instances
-
A dedicated
VPCNetwork. - Masters load balancer to balance API requests and the Red Hat OpenShift Container Platform web console.
- Applications load balancer to balance incoming connections to applications running in Red Hat OpenShift Container Platform.
- Red Hat OpenShift Container Platform routers and registry running in the infrastructure nodes.
- Dedicated storage for the Red Hat OpenShift Container Platform registry.
- Dedicated storage for container images on all nodes.
- Dedicated storage for pods' local storage on all nodes.
-
Dedicated storage for
etcddata on all masters. - Dynamic storage for applications.
- External IP addresses for bastion, masters load balancer and applications load balancer.
- Red Hat OpenShift Container Platform SDN for pod to pod communication.
Older versions of this reference architecture contained glue code to deploy Red Hat OpenShift Container Platform instances, load balancers, etc. using the OpenShift-Ansible-Contrib repository not officially supported by Red Hat. This new reference architecture uses Google Cloud Platform command line tools as an example on how to create all the required infrastructure elements in Google Cloud Platform providing more flexibility and customization to deploy the infrastructure required but in a more manual way. Red Hat efforts are focused on having an automated and supported procedure to deploy a proper Red Hat OpenShift Container Platform on different providers.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.