We are excited to announce the General Availability (GA) of the Azure Red Hat OpenShift (ARO) landing zone accelerator within the Cloud Adoption Framework. Landing zone accelerators provide architectural guidance, reference architecture, reference implementations and automation packaged to deploy workload platforms in Azure at scale and aligned with industry proven practices. Like other Landing zone accelerators, the ARO guide delivers resources that help design, deploy, and maintain well Architected ARO platforms. These resources include:
ARO landing zone accelerator documentation
ARO landing zone accelerator reference implementation
The ARO landing zone accelerator documentation provides a conceptual architecture that can be a great starting point for ARO workloads. Understanding that most workloads are managed by a cross functional team, this modular approach by critical design areas such as security, management, network topology etc. allows a separation of concern so that various teams can focus on the area of the workload platform that they are responsible for. The documentation was developed by a team of subject matter experts with extensive experience building solutions on ARO for themselves and Azure customers.
The reference implementation, hosted on GitHub, builds on the documentation, and provides step by step approaches to deploy secure ARO workload platforms. Users of the reference implementation can follow modularized steps which can be customized to fit their specific needs as they are designed to be easily extensible. As of the time of its launch, the ARO secure baseline is available with the deployment options being Azure CLI and Terraform. Below is the reference implementation’s architecture:
The application development team you work with has decided to migrate their existing application hosted on Red Hat OpenShift virtual machines from on premises to the cloud. The main reasons for this migration are to improve scalability, eliminate the cost and complexity of maintaining physical servers themselves, provide a better service experience to their customers in different continents and take advantage of the agility that comes with building cloud native applications using container technologies. The operations team has been learning the basics of public clouds, containers and Kubernetes and are confident that they can manage Kubernetes infrastructure on the cloud. After reviewing various options, they have decided to migrate their existing workload to Azure Red Hat OpenShift and need guidance on the best way to get started.
Azure Red Hat OpenShift provides highly available, fully managed OpenShift clusters on demand, monitored and operated jointly by Microsoft and Red Hat. OpenShift brings added-value features to complement Kubernetes, making it a turnkey container platform as a service (PaaS) with a significantly improved developer and operator experience. As a solution architect, you’ll need to consider the ARO operator’s role of providing a cost effective yet scalable and secure platform for your development team.
Using the self-service solution that is the ARO landing zone accelerator, you can learn some of the important architectural considerations and recommendations that need to be decided upon to ensure you are deploying your ARO platform the right way. You can explore the critical design areas and make important decisions based on the guidance. When it is time for deployment, you don’t have to start from scratch. Instead, you have ready to deploy Terraform templates as well as Azure CLI deployment steps that can significantly speed up your journey to production. You add a backlog item to periodically revisit the guidance to make sure your site's workload platform is incorporating any new recommendations and to evaluate any architectural changes made to the platform since it was last reviewed, knowing the landing zone accelerator will continue to evolve with ARO.
Ayobami Ayodeji is a Senior Program Manager who leads teams that create technical assets to support architecture guidance around Azure’s container related services. He also leads the architecture review board for container workloads in Azure Architecture Center.