Lab - Intro to Azure RedHat OpenShift (ARO)

Let's find out the differences with Azure Kubernetes Service (AKS)

Lab - Intro to Azure Kubernetes Service (AKS)

Intro

Prerequisites

Resources

Creating an ARO cluster

Setup

In your bash console, set the following variables:

LOCATION=eastus
RESOURCEGROUP=aro-rg
CLUSTER=cluster

Verify your vCPU quota is sufficient to deploy ARO (at least 40 vCPUs):

az vm list-usage -l $LOCATION \
--query "[?contains(name.value, 'standardDSv3Family')]" \
-o table

Register necessary resource providers in your Azure Subscription:

az provider register -n Microsoft.RedHatOpenShift --wait
az provider register -n Microsoft.Compute --wait
az provider register -n Microsoft.Storage --wait
az provider register -n Microsoft.Authorization --wait

Deploy the foundation

Create a resource group:

az group create \
  --name $RESOURCEGROUP \
  --location $LOCATION

Create a virtual network:

az network vnet create \
   --resource-group $RESOURCEGROUP \
   --name aro-vnet \
   --address-prefixes 10.0.0.0/22

Create an empty subnet for the master nodes:

az network vnet subnet create \
  --resource-group $RESOURCEGROUP \
  --vnet-name aro-vnet \
  --name master-subnet \
  --address-prefixes 10.0.0.0/23 \
  --service-endpoints Microsoft.ContainerRegistry

Create an empty subnet for the worker nodes:

az network vnet subnet create \
  --resource-group $RESOURCEGROUP \
  --vnet-name aro-vnet \
  --name worker-subnet \
  --address-prefixes 10.0.2.0/23 \
  --service-endpoints Microsoft.ContainerRegistry

Disable subnet private endpoint policies on the master subnet:

az network vnet subnet update \
  --name master-subnet \
  --resource-group $RESOURCEGROUP \
  --vnet-name aro-vnet \
  --disable-private-link-service-network-policies true

Create the cluster

Run the following command to create your cluster. Ensure that @pull-secret.txt is the actual path to your pull secret file that you downloaded during the prerequisites.

az aro create \
  --resource-group $RESOURCEGROUP \
  --name $CLUSTER \
  --vnet aro-vnet \
  --master-subnet master-subnet \
  --worker-subnet worker-subnet \
  --pull-secret @pull-secret.txt

Once you run az aro create, it usually takes around 30 minutes for the cluster to be fully operational. Once it’s ready, continue to the next section to connect to your cluster.

Connecting to an ARO cluster

Web Console

Obtain the web console URL for your cluster:

az aro show \
    --name $CLUSTER \
    --resource-group $RESOURCEGROUP \
    --query "consoleProfile.url" -o tsv

Open the link that is returned in your browser.

Return to your terminal and obtain the credentials to your cluster:

az aro list-credentials \
  --name $CLUSTER \
  --resource-group $RESOURCEGROUP

The credentials you just received can be used to log into the web console. Return to your browser and give it a try!

Command Line

Install the appropriate version of the OpenShift CLI tool for your machine.

Retrieve the address of you OpenShift API:

apiServer=$(az aro show -g $RESOURCEGROUP -n $CLUSTER --query apiserverProfile.url -o tsv)

Obtain the credentials to your cluster:

az aro list-credentials \
  --name $CLUSTER \
  --resource-group $RESOURCEGROUP

Log in to your cluster:

oc login $apiServer -u kubeadmin -p <kubeadmin password>

Connecting an ARO cluster to the Hybrid Cloud Console

Obtain the pull secrets file from your cluster. The following command saves this as a JSON file.

oc get secrets pull-secret -n openshift-config -o template='' | base64 -d > pull-secrets.json

Open pull-secrets.txt that you previously obtained from console.redhat.com and copy the cloud.openshift.com object from that file into `pull-secrets.json. Once done, validate your json with the following command:

cat pull-secrets.json | jq

And lastly, push that json file back to your cluster with the following command:

oc set data secret/pull-secret -n openshift-config --from-file=.dockerconfigjson=./pull-secrets.json

After a few moments, you can visit the Red Had Hybrid Cloud Console and view your cluster and all the telemetry being sent there.

Deploy an application to ARO

In this example, we will deploy a sample website:

oc run party-clippy --image=r.j3ss.co/party-clippy

Now that the website is deployed, we can expose it to the internet. Let’s create a Kubernetes service:

oc expose pod/party-clippy --port 80 --target-port 8080 --type LoadBalancer

Now we need to obtain the IP Address where our website is available. Run the following command and obtain the EXTERNAL-IP address. You may need to wait a few moments for the external IP Address to be populated.

oc get service/party-clippy

Open up your browser, type in the IP Address.

Hello Clippy!

 _________________________________
/ It looks like you're building a \
\ microservice.                   /
 ---------------------------------
 \
  \
     __
    /  \
    |  |
    @  @
    |  |
    || |  /
    || ||
    |\_/|
    \___/

Clean-Up

Once you are ready to dispose of your ARO cluster, you can run the following command:

az aro delete --resource-group $RESOURCEGROUP --name $CLUSTER

Upon completion, all resources belonging to your ARO cluster will be deleted.

Back to homepage