Merge pull request #8 from kthcloud/install-k8s-cluster-new

Fix typos in KubeVirt blog post and host provision guide

hugo/content/News/2024-04-14.md

@@ -14,7 +14,7 @@ KubeVirt is a virtualization add-on for Kubernetes that allows you to run virtua
 <img src="../../images/blog/kubevirt_overview.png" alt="kubevirt overview" /><br/>
 
 ## Our solution
-When moving away from CloudStack it was imperative that we found a solution that was easy to manage and maintain. Since KubeVirt is built on top of Kubernetes, it meant we could harness any platform that support Kubernetes. We decided to use Rancher to manage our Kubernetes clusters, as it provides a user-friendly interface and simplifies the management of our clusters. While Rancher offer Kubernets cluster creation tools, the last crux involved how Rancher itself would be managed. We decided to use K3s and called the cluster the `sys-cluster`. Any cluster that is then created using Rancher is called a `deploy-cluster`. The sys-cluster is only managed in our main zone `se-flem`, while deploy-clusters are created in all zones.
+When moving away from CloudStack it was imperative that we found a solution that was easy to manage and maintain. Since KubeVirt is built on top of Kubernetes, it meant we could harness any platform that support Kubernetes. We decided to use Rancher to manage our Kubernetes clusters, as it provides a user-friendly interface and simplifies the management of our clusters. While Rancher offer tools for creating and managing the entire life cycle of a Kubernetes cluster, it left us with one last crux: How would the cluster hosting Rancher be created? We opted for the light weight route and chose to use K3s, a Kubernetes distribution that is easy to install and manage. This means we were able to spin up a K3s cluster in no time and install Rancher on top of it. We called this cluster the `sys-cluster`. The sys-cluster thus forms the foundation for all our other clusters that Rancher will manage, which we call `deploy-clusters`. To keep things simple, we decided to only run the sys-cluster in the main zone `se-flem`. 
 
 ## Progress so far
 We have been working on this project for a few months now and have made significant progress. We have set up a new sys-cluster in the `se-flem` zone using K3s and Rancher that will be used to manage our deploy-clusters. We have also set up a deploy-cluster in the `se-flem` zone, which is currently running KubeVirt. The `se-kista` zone will be set up once we have completed the migration of all hosts in the `se-flem` zone (apart from the management server for CloudStack, which will be migrated last).

hugo/content/maintenance/hostProvisioning.md

@@ -42,14 +42,14 @@ host.
     6.  Click `Save machine`\
         The machine will be started by IPMI and will PXE-boot into commissioning
 5.  Deploy the machine
-    1.  Ensure the machine is turned off
+    1.  Ensure the machine is in `Ready` state
     2.  Go to the machine in MaaS
     3.  Go to the `Network Tab`
     4.  Find the connected NIC and in the drop-down menu click `Edit Phyiscal`
     5.  Select `Fabric` for the zone, eg. `se-flem`
     6.  Select `Subnet` for the zone, eg. `172.31.0.0/16`
     7.  Select `Static assign` in `IP mode`
-    8.  Enter the statis IP address of the host in `IP address`
+    8.  Enter the static IP address of the host in `IP address`
     9.  Click `Save interface`
     10. Click `Take action` and `Deploy` and tick `Cloud-int user-data`
     12. Upload or paste the cloud-init file generated in **step 2**