Minor quality improvement.

This commit is contained in:
savagebidoof 2023-08-01 20:10:40 +02:00
parent 1454839692
commit d39ee6ebc2

View File

@ -208,9 +208,9 @@ Current Issue? For X and y, I need to wait for a while for the DNS provider to r
### Part 5
- [ ] Explore Pi4 Storage options.
- [x] Explore Pi4 Storage options.
- [ ] Consider Storage options for the OrangePi5.
- [x] Consider Storage options for the OrangePi5.
#### Rollback plan
@ -218,7 +218,8 @@ Current Issue? For X and y, I need to wait for a while for the DNS provider to r
### Part 6
- [ ] ~~Wipe~~ (**don't wipe** just use a different drive) and recreate the current `Kluster`, this time using the Pi4 as a _master_, and the 2 Orange Pi5 as _slaves_ (this will require updating the DNS/DHCP local services).
- [x] ~~Wipe~~ (**don't wipe** just use a different drive) and recreate the current `Kluster`, this time using the Pi4 as a _master_, and the 2 Orange Pi5 as _slaves_ (this will require updating the DNS/DHCP local services).
- [ ] Deploy all the services from the previous Kubernetes cluster to the new one.
> **Note**:\
> I can make a new cluster on the Pi4, and remove the taint that prevents from scheduling pods on that node. Deploy everything inside (a well a LB with the same exact IP than the current one, and proceed to stop the Orange PI 5), then "reformat" the OPi5s with a new distro, install stuff etc., and join them to the cluster running on the Pi4.
@ -229,11 +230,14 @@ Current Issue? For X and y, I need to wait for a while for the DNS provider to r
### Part 7
- [ ] Deploy NFS service on the `media SRV` host.
- [ ] Remove the last host from the old kubernetes cluster and join it to the new cluster.
### Part 8
- [ ] Deploy NFS service on the `media SRV` host.
### Part 9
- [ ] Deploy Istio security.
### Part 10
@ -1428,7 +1432,6 @@ node "slave01.filter.home" deleted
### Part 6
Currently, the resources whereas:
```yaml