Routine automated backups
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- google-cloud, kubernetes
- Domain
- cloud, devops, infrastructure
Research direction
No files, tests, or entry points are named. Start by comparing GKE-level disk backups, Jenkins and Artifactory plugins, and cloud storage buckets against the stated need to preserve history and manually published artifacts. Done means selecting and documenting a routine backup approach for at least Jenkins and Artifactory.
Written by the indexing model from the issue text.
Description
As part of the 2023 overhaul I aim to at least take GKE-level backups of the disks for the major tools after final deployment (Jenkins and Artifactory at least). There are a variety of options for routine backups - although the new IaC/CaC focus takes a huge bite out of just redeploying from scratch and being able to get up to speed fairly fast. Still, it would be unnecessary pain to lose all history in Jenkins and especially Artifactory, where we might also have a few manually published artifacts that snuck in over the years.
There are plugins for the individual apps as well as GKE-provided backups but I'm unsure about which options to pick.
Another related option would be to offload binaries to cloud-provided storage buckets rather than local / persistent disks, those are backed up at the cloud-provider level and may be secure enough to only worry about having the config in a good place.
- Dominant language
- Groovy
- Stars
- 0
- Forks
- 2
- Avg merge
- 14m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MovingBlocks/Logistics
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MovingBlocks/Logistics#11 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MovingBlocks/Logistics#5 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in MovingBlocks/Logistics
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langflow-ai/openrag#2454 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
earendil-works/pi#10324 · 1 comment ·
Maintainers usually reply within 1 day
-
area: tooling status: accepting prs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SquiggleTools/SquiggleConf.com#185 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day