etcd-io/etcd

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

Open

#20623 opened on Sep 8, 2025

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

Description

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

Contributor guide

Tech stack
go
Domain
backendtesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programmingUnderstanding of etcd architectureFamiliarity with Kubernetes traffic patterns
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
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.