etcd-io/etcd

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

Open

#20,623 opened on Sep 8, 2025

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

Repository metrics

Stars
 (51,701 stars)
PR merge metrics
 (Avg merge 6d 3h) (71 merged PRs in 30d)

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

Research direction
Investigate the referenced Kubernetes PRs (#133873 and #132355) to understand the current state of keys only and Count calls. Check if the etcd traffic generator already handles Keys and Count appropriately. Determine if this issue is still relevant or if it can be closed.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Mostly clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50