k8s.io/client-go/util/retry.RetryOnConflict
third-partyThe 1862nd most-called third-party function by production calls. Called 402 times across 28 modules; 343 of those run outside tests and generated code.
No change in production calls since 2026-W39.
- prod calls
- 343
- non-test, non-generated
- all calls
- 402
- total callsites
- modules
- 28
- distinct callers
- in loop
- 5%
- of prod calls
- in tests
- 15%
- 59 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function29%A direct call to an exported package function, resolved by type.
- Package function (by syntax)71%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into RetryOnConflict from notable Go projects. Open one on the map to see what else it hammers.
- Kubernetes 226 66%
- Argo 10 3%
- Traefik 7 2%
- Kyverno 4 1%
- Velero 4 1%
where it's called
Callsites in the wild
12 representative callsites of 402, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
-
kubesphere/kubesphere @v0.0.0-20260715011438-04a29b5c6014
in loop - in loop
-
sigs.k8s.io/controller-runtime @v0.25.1
pkg/envtest/crd.go:264
in loop - in loop
- in loop
-
kubernetes/kubernetes @master
staging/src/k8s.io/cloud-provider/controllers/route/route_controller.go:479 ↗
in loop - in loop
-
kubesphere/kubesphere @v0.0.0-20260715011438-04a29b5c6014
in loop - in loop
- in loop
top callers
The modules that reach for it
The modules that call RetryOnConflict most in this snapshot.
- github.com/kubernetes/kubernetes13634%
- k8s.io/kubernetes12130%
- github.com/rook/rook215%
- github.com/kubesphere/kubesphere143%
- github.com/fission/fission123%