[M8.3b] Control plane and agent upgrades

Open
  • Is something wrong?
#240 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, ubuntu
Domain
devops, infrastructure

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.