Prepare scripts to move drbd primary #1
Labels
No labels
bug
cleanup
duplicate
enhancement
forgefriends
help wanted
hetzner
invalid
label workflow
need more info
question
refactor
static-site
sync
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infrastructure/k8s-cluster#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
See also https://invisible.forgejo.org/infrastructure/k8s-cluster/src/branch/main/k8s-maintenance.md
Steps
forgejo.org/drbd=primarylabelforgejo.org/drbd=primarylabel to new primarythis way we don't need to move all instances to nfs before maintenace. We need to drain anyways if nfs stops because of drbd move.
Maybe it's easier to just scale down deployments / statefulsets / ..., which have pvc on drbd / nfs.
That ways it's more easy. 🤔
@earl-warren can we at least have a more extensive description on how to proceed this?
Especially when we also need to move the floating ip.
I added a link to https://invisible.forgejo.org/infrastructure/k8s-cluster/src/branch/main/k8s-maintenance.md in the description to remember where those improvements should go.
I thought of planning a disaster recovery exercise and improve the documentation at the same time? End of July would work for me (i.e. after the v12 release is published and the dust settles). What do you think?
sounds good