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

Continue work on exercise 4.

Browse Source
This commit is contained in:
James Blair
2024-05-27 09:13:31 +12:00
parent f9c7fbcf26
commit 679efe5bda
3 changed files with 9 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
data/workshop/exercise2.mdx
View File

@ -98,3 +98,5 @@ oc create secret generic cloud-private-key \
|:-----------------------------------------------------------------------------:| |:-----------------------------------------------------------------------------:|
| *Create a private key secret* | | *Create a private key secret* |
</Zoom> </Zoom>
Once your network configuration, operator installation and secret creation are complete you're ready to move on to the next exercise 🎉

7
data/workshop/exercise3.mdx
View File

@ -121,4 +121,9 @@ Within OpenShift you can then click the ➕ button in the top right hand corner,
## 3.2 Verify windows machine status ## 3.2 Verify windows machine status
> After creating the `MachineSet` a new Windows machine will be automatically provisioned and added to our OpenShift cluster, as we set our desired replicas in the YAML to `1`.
Creating, provisioning and configuring a new Windows host can be a lengthy process taking 15-30 minutes so now is a good time to take a break ☕.
You can keep an eye on the status of your Machine in the OpenShift web console. Once it reaches the **Provisioned as node** status you are ready to proceed to the next exercise.

46
data/workshop/exercise4.mdx
View File

@ -52,48 +52,4 @@ This will allow us to deploy any helm charts available in this repository.
</Zoom> </Zoom>
## 4.2 Deploy candystore helm chart
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.
Below is a yaml snippet we will use as base to create our `MachineSet`:
```yaml
metadataServiceOptions: {}
tags:
- name: kubernetes.io/cluster/cluster-<id>
value: owned
deviceIndex: 0
ami:
id: ami-0e76083a67107f741
subnet:
filters:
- name: 'tag:Name'
values:
- cluster-<id>-private-ap-southeast-<zone>
apiVersion: awsproviderconfig.openshift.io/v1beta1
iamInstanceProfile:
id: cluster-<id>-worker-profile
```
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:
```bash
name=$(oc get machineset -A -o jsonpath={.items[0].metadata.name})
echo "Cluster id is: ${name:8:11}"
echo "Cluster availability zone is: ${name:40:2}"
```
After retrieving your cluster id and zone update the sample `MachineSet` using your preferred text editor, then select and copy all of the text to clipboard.
Within OpenShift you can then click the ➕ button in the top right hand corner, paste in your yaml and click **Create**.
```
<Zoom>
|![workshop](/workshops/static/images/windows/create-machineset.gif) |
|:-----------------------------------------------------------------------------:|
| *Create a windows machineset* |
</Zoom>