From ac3e2c4f24915b47d67e0b0a4d589e8ec55443f6 Mon Sep 17 00:00:00 2001 From: James Blair Date: Mon, 27 May 2024 10:46:37 +1200 Subject: [PATCH] Fix some typos. --- data/workshop/exercise2.mdx | 4 ++-- data/workshop/exercise3.mdx | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/data/workshop/exercise2.mdx b/data/workshop/exercise2.mdx index 027f66a..0017fae 100644 --- a/data/workshop/exercise2.mdx +++ b/data/workshop/exercise2.mdx @@ -24,7 +24,7 @@ To install Operators on OpenShift we use Operator Hub. A simplistic way of think ## 2.1 - Enable hybrid networking -Before installing the windows maching config operator our first step as a cluster administrator is configure a our OpenShift cluster network to allow Linux and Windows nodes to host Linux and Windows workloads, respectively. +Before installing the windows machine config operator our first step as a cluster administrator is configure a our OpenShift cluster network to allow Linux and Windows nodes to host Linux and Windows workloads, respectively. This requires enabling a feature called **[hybrid overlay networking](https://docs.openshift.com/container-platform/4.15/networking/ovn_kubernetes_network_provider/configuring-hybrid-networking.html#configuring-hybrid-ovnkubernetes)**. @@ -75,7 +75,7 @@ Follow the steps below to install the operator: | *Installing the windows machine config operator* | -> Note: The operator installation may take several minutes to complete. Wait for the status of `succeeded` before continuing with the following step. +> Note: The operator installation may take several minutes to complete. Wait for the status of `✅ succeeded` before continuing with the following step. > ## 2.3 - Create configuration secrets diff --git a/data/workshop/exercise3.mdx b/data/workshop/exercise3.mdx index 8dd39e5..be44628 100644 --- a/data/workshop/exercise3.mdx +++ b/data/workshop/exercise3.mdx @@ -26,9 +26,9 @@ The two primary resources are: ## 3.1 Create a single replica machineset -In this excersie we will create a `MachineSet`. Once created this will automatically begin provisoning a Windows machine and adding it to our cluster as a worker node. +In this exercise we will create a `MachineSet`. Once created this will automatically begin provisoning a Windows machine and adding it to our cluster as a worker node. -Below is a yaml snippet we will use as base to create our `MachineSet`: +Below is a YAML snippet we will use as base to create our `MachineSet`: ```yaml apiVersion: machine.openshift.io/v1beta1 @@ -100,7 +100,7 @@ spec: There are ten references to `` in the sample that we need to find & replace with the actual cluster id for the cluster we have been allocated for the workshop and five references to the availability `` for our cluster nodes that we also need to update with our actual zone in use. -Run the following command in your bastion host to find your cluster id and zone: +Run the following command in your bastion host terminal session to find your cluster id and zone: ```bash name=$(oc get machineset -A -o jsonpath={.items[0].metadata.name})