Azure Red Hat OpenShift —Terraformization

I’ve previously shared with you both of an old-school Shell script and a profound explanation on how we can cook an Azure Red Hat OpenShift cluster. The purpose was mainly to make a better understanding on how easily the deployment of Azure Red Hat OpenShift is.

Today, I‘m back with a fresh post, to explain how I managed to automate the provisioning of an Azure Red Hat OpenShift cluster. This including its integration with different sets of Azure components, such as Azure Active Directory, Azure Log Analytics and a VNET Peering with a Hub Virtual Network, our network aggregation layer.

The acronym “ARO” is used in the following as an abbreviation for “Azure Red Hat OpenShift”.

Automation?

Automation still sounds overwhelming but offers scalable benefits to modern enterprises, especially in term of time-saving and cost-effectiveness.

ARO, as a managed solution is already easy to deploy and requires straight forward steps. So, why shall we automate its deployment?

Well, there is no obligation to do so ;) but, this has its benefits for businesses looking to provision a bunch of ARO clusters worldwide. Automation here helps to simplify recurring activities and eliminates the chance of errors by ensuring consistency in performing those deployments.

“You should spend more time developing your business rather than caring about the…