Added rollback plans and separated by parts.
This commit is contained in:
parent
b68c363cd8
commit
25091d6a56
@ -74,6 +74,13 @@ Slave01: 192.168.1.11
|
||||
|
||||
## Procedure
|
||||
|
||||
> Note:\
|
||||
> I will be making backups of certain configurations before modifying them, yet I won't be displaying it for the sake of reducing a bit the amount of text dumped here.
|
||||
|
||||
### Part 1
|
||||
|
||||
> Completed 19/July/2023
|
||||
|
||||
- [x] Move local DHCP and DNS to the host `srv`.
|
||||
|
||||
- [x] Move Gitea to the host `srv`.
|
||||
@ -82,6 +89,20 @@ Slave01: 192.168.1.11
|
||||
|
||||
- [X] Update Traefik ingress configs
|
||||
|
||||
#### Rollback plan
|
||||
|
||||
> Not required.
|
||||
|
||||
- Launch the services in the `Pi4` server.
|
||||
|
||||
- Return the Traefik configuration to the previous one.
|
||||
|
||||
- Modify the DNS configurations (if applicable).
|
||||
|
||||
### Part 2
|
||||
|
||||
[//]: # (> Started 19/July/2023)
|
||||
|
||||
- [ ] Deploy Certificate Manager on the current `Kluster` with let's encrypt certificate provisioning.
|
||||
|
||||
- [ ] Deploy an Istio Ingress to allow access to the Gitea service.
|
||||
@ -90,24 +111,52 @@ Slave01: 192.168.1.11
|
||||
|
||||
- [ ] Ensure the Certificates are being provisioned.
|
||||
|
||||
#### Rollback plan
|
||||
|
||||
- As much, delete the deployed configurations.
|
||||
|
||||
### Part 3
|
||||
|
||||
- [ ] Configure Istio to route traffic towards Jellyfin and Filebrowser services.
|
||||
|
||||
- [ ] Backup the Istio/Kubernetes configurations used.
|
||||
|
||||
#### Rollback plan
|
||||
|
||||
- As much, delete the deployed configurations.
|
||||
|
||||
### Part 4
|
||||
|
||||
- [ ] Explore Pi4 Storage options.
|
||||
|
||||
- [ ] Consider Storage options for the OrangePi5.
|
||||
|
||||
- [ ] Wipe 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).
|
||||
#### Rollback plan
|
||||
|
||||
- Return the acquired drives to Amazon?
|
||||
|
||||
### Part 5
|
||||
|
||||
- [ ] ~~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).
|
||||
|
||||
- [ ] Update the `Current Setup` documentation with the new container and architecture rearrangement.
|
||||
|
||||
- [ ] Deploy NFS service on the `media SRV`.
|
||||
- [ ] Deploy NFS service on the `media SRV` host.
|
||||
|
||||
- [ ] Migrate some lightweight/not data heavy services from the `media SRV` to the `Kluster`.
|
||||
|
||||
- [ ] Update the `Current Setup` documentation with the new container and architecture rearrangement.
|
||||
|
||||
#### Rollback plan
|
||||
|
||||
- Revert orange Pi 5 to the previous drive.
|
||||
|
||||
- Revert Pi4 to the previous drive.
|
||||
|
||||
- Delete the NFS service deployed.
|
||||
|
||||
- Run the old migrated services back on the `media SRV` host.
|
||||
|
||||
## Execution
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user