etcd-io/etcd

[robustness tests] Consider adding Keys, Count to Kubernetes traffic generator

Open

#20,623 opened on 2025年9月8日

GitHub で見る
 (5 comments) (0 reactions) (0 assignees)Go (51,701 stars) (10,352 forks)batch import
area/robustness-testinghelp wantedtype/feature

説明

What would you like to be added?

Kubernetes traffic generator should use Count of Kubernetes-Etcd interface and invoke Ranges with keys_only to better simulate actual Kubernetes traffic.

It seems that keys_only Range calls will be unlikely in the future due to https://github.com/kubernetes/kubernetes/pull/133873.

Work in https://github.com/kubernetes/kubernetes/pull/132355 also replaced calls to Count so it is likely the work on this may no longer be needed/useful.

Why is this needed?

Part of https://github.com/etcd-io/etcd/issues/15820 and https://github.com/etcd-io/etcd/issues/20182

コントリビューターガイド

技術スタック
go
領域
backendtesting
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
needs maintainer response
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
Go programmingUnderstanding of etcd architectureFamiliarity with Kubernetes traffic patterns
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
15
調査方針
This issue proposes adding Keys and Count to the Kubernetes traffic generator in etcd's robustness tests. However, the issue notes that recent PRs (kubernetes/kubernetes#133873 and kubernetes/kubernetes#132355) may make this work unnecessary. First, check the status of those PRs and confirm with maintainers whether this feature is still desired. If so, examine the existing traffic generator code (likely in the tests directory) to understand how to integrate these operations. The discussion in the issue comments may provide further guidance.