1
0

doco typos

This commit is contained in:
michael 2022-11-02 01:04:30 +13:00
parent 9fb0635789
commit a8edbf45d6

View File

@ -4,14 +4,14 @@ With some adjustments though this could be used to provision multiple hypervisor
An outline of the steps, which are roughly broekn up by playbook: An outline of the steps, which are roughly broekn up by playbook:
- [] Install Arch linux on the bare metal - [ ] Install Arch linux on the bare metal
- [x] Configure the bare metal Arch host as a hypervisor (qemu/kvm) - [x] Configure the bare metal Arch host as a hypervisor (qemu/kvm)
- [] Install Arch linux into a VM on the hypervisor then convert it to a template. - [ ] Install Arch linux into a VM on the hypervisor then convert it to a template.
- [x] Deploy 3 (or more) VMs from the template (uses backing store qcow images). - [x] Deploy 3 (or more) VMs from the template (uses backing store qcow images).
- [x] Create a kubernetes cluster from those 3 VMs. - [x] Create a kubernetes cluster from those 3 VMs.
- [x] Install calico networking into the cluster. - [x] Install calico networking into the cluster.
- [] Remove the taint from control plane nodes. <-- Optional - [ ] Remove the taint from control plane nodes. <-- Optional
- [] Deploy workloads into the cluster - [ ] Deploy workloads into the cluster
What you don't see here is setup/configuration of an Opnsense VM to act as a firewall, this is too far off from being possible to automate. What you don't see here is setup/configuration of an Opnsense VM to act as a firewall, this is too far off from being possible to automate.