Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Routine automated backups

未关闭
#3 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
google-cloud, kubernetes

调研方向

未指定任何文件、测试或入口点。首先将 GKE 级别的磁盘备份、Jenkins 和 Artifactory 插件以及云存储桶与所述的保留历史记录和手动发布制品的需求进行比较。完成的标准是选择并记录至少针对 Jenkins 和 Artifactory 的例行备份方案。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Groovy
星标
0
派生
2
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

MovingBlocks/Logistics 的其他 Issue

查看 MovingBlocks/Logistics 的全部 Issue

相似的 Issue

更多 Cloud Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。