When to Use
- ARO cluster provisioning
- Cluster configuration
- OpenShift-specific setup
Prerequisites
- Azure CLI authenticated
- OpenShift CLI installed
- ARO resource provider registered
- Sufficient quota for Worker VMs
Commands
Pre-deployment Checks
# Check ARO resource provider
az provider show -n Microsoft.RedHatOpenShift --query "registrationState"
# Check quota
az vm list-usage --location eastus2 -o table
Cluster Deployment
# Create resource group
az group create --name rg-aro --location eastus2
# Create virtual network
az network vnet create \
--name vnet-aro \
--resource-group rg-aro \
--address-prefixes 10.0.0.0/22
# Create master subnet
az network vnet subnet create \
--name master-subnet \
--resource-group rg-aro \
--vnet-name vnet-aro \
--address-prefixes 10.0.0.0/23
# Create worker subnet
az network vnet subnet create \
--name worker-subnet \
--resource-group rg-aro \
--vnet-name vnet-aro \
--address-prefixes 10.0.2.0/23
# Create ARO cluster
az aro create \
--name aro-cluster \
--resource-group rg-aro \
--vnet vnet-aro \
--master-subnet master-subnet \
--worker-subnet worker-subnet \
--pull-secret @pull-secret.txt
Post-deployment
# Get cluster credentials
az aro list-credentials --name aro-cluster --resource-group rg-aro
# Get console URL
az aro show --name aro-cluster --resource-group rg-aro --query "consoleProfile.url" -o tsv
# Get API server URL
az aro show --name aro-cluster --resource-group rg-aro --query "apiserverProfile.url" -o tsv
Best Practices
- Configure pull-secret for Red Hat registry access
- Enable private cluster for production
- Integrate with Azure AD for authentication
- Configure appropriate worker VM SKUs
Output Format
- Deployment steps completed
- Cluster credentials
- Console and API URLs
- Next steps for configuration
Integration with Agents
Used by: @platform, @terraform
Converted and distributed by TomeVault — claim your Tome and manage your conversions.