etcd-io/etcd

[test] support cluster-api style rolling replacement upgrade

Open

#20,804 建立於 2025年10月15日

在 GitHub 查看
 (8 留言) (0 反應) (1 負責人)Go (51,701 star) (10,352 fork)batch import
area/testinghelp wantedstage/trackedtype/feature

描述

What would you like to be added?

Currently our e2e framework supports in-place upgrade. We just replace the binary, and reuse the existing data.

https://github.com/etcd-io/etcd/blob/30452ab110473eda5f60bdb301c046194a154e91/tests/framework/e2e/downgrade.go#L131

However, the cluster-api/Kubeadm upgrades Kubernetes cluster in a rolling replacement approach,

  • add a new learner first;
  • promote it later
  • remove an old node
  • repeat the above steps until all nodes are replaced.

The key difference is the new member(learner) gets started without local data, so it may receive a snapshot from the leader.

We should update our e2e test framework to support both upgrade approaches,

  • rolling in-place upgrade
  • rolling replacement upgrade

Why is this needed?

To improve test coverage.

貢獻者指南

技術棧
go
領域
testing
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingetcd e2e test frameworkrolling upgrade concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Study the existing e2e upgrade test framework in tests/framework/e2e/downgrade.go (linked). Understand the current in place upgrade flow. Research cluster api's rolling replacement approach for Kubernetes upgrades. Then implement a similar pattern for etcd, adding a new learner, promoting it, and removing old nodes.