jmhbnz/workshops
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix some typos.

Browse Source
This commit is contained in:
James Blair
2024-05-27 10:46:37 +12:00
parent a63205d940
commit ac3e2c4f24
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
data/workshop/exercise2.mdx
View File

@ -24,7 +24,7 @@ To install Operators on OpenShift we use Operator Hub. A simplistic way of think
## 2.1 - Enable hybrid networking ## 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)**. 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* | | *Installing the windows machine config operator* |
</Zoom> </Zoom>
> 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 ## 2.3 - Create configuration secrets

6
data/workshop/exercise3.mdx
View File

@ -26,9 +26,9 @@ The two primary resources are:
## 3.1 Create a single replica machineset ## 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 ```yaml
apiVersion: machine.openshift.io/v1beta1 apiVersion: machine.openshift.io/v1beta1
@ -100,7 +100,7 @@ spec:
There are ten references to `<id>` 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 `<zone>` for our cluster nodes that we also need to update with our actual zone in use. There are ten references to `<id>` 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 `<zone>` 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 ```bash
name=$(oc get machineset -A -o jsonpath={.items[0].metadata.name}) name=$(oc get machineset -A -o jsonpath={.items[0].metadata.name})