[M8.3b] Control plane and agent upgrades

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, ubuntu

调研方向

Read deploy/control-plane.Dockerfile and release.yml, then trace the UpgradeControlPlane and UpgradeAgent actions and the existing VM tests. The issue depends on M5.4 and is blocked by the test VM issue, so start there to find the upgrade flow and test setup. Done means upgrading a VM from the previous release succeeds, and a forced failure automatically rolls back.

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

描述

blocked priority:P1 security-review task track:agent track:cross-cutting
Task id

M8.3b

Track

X: cross-cutting, A: agent

Scope
  • deploy/control-plane.Dockerfile, Trivy image scan in release.yml, UpgradeControlPlane action with snapshot and rollback; UpgradeAgent with signature check and rollback to the previous binary.
  • shipkeep-build user, cgroup v2 delegation, AppArmor profile on Ubuntu 24.04, conflict detection.
Acceptance criteria

Upgrade from previous release to current on a VM, then forced failure triggers automatic rollback.

Depends on

M5.4

Blocked by

The test VM issue.

主要语言
TypeScript
星标
2
派生
1
平均合并
7 小时 17 分钟
30 天内合并 PR
197

环境准备

从这里开始

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

shipkeepdev/shipkeep 的其他 Issue

查看 shipkeepdev/shipkeep 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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