Skip to content
callcount

k8s.io/apimachinery/pkg/api/meta.FindStatusCondition

third-party

The 8718th most-called third-party function by production calls. Called 159 times across 13 modules; 69 of those run outside tests and generated code.

No change in production calls since 2026-W37.

All of k8s.io/apimachinery/pkg/api/meta → Docs on pkg.go.dev ↗

prod calls
69
non-test, non-generated
all calls
159
total callsites
modules
13
distinct callers
in loop
6%
of prod calls
in tests
57%
90 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 function43%A direct call to an exported package function, resolved by type.
  • Package function (by syntax)57%A package function in a module outside the crawl, keyed by import path.

who calls this

Notable callers

Production calls into FindStatusCondition from notable Go projects. Open one on the map to see what else it hammers.

where it's called

Callsites in the wild

12 representative callsites of 159, prioritizing in-loop and non-test usage. We link to source, never display it.

FindStatusCondition · 12 of 159 callsites

top callers

The modules that reach for it

The modules that call FindStatusCondition most in this snapshot.

  • github.com/kubevirt/kubevirt2415%
  • kubevirt.io/kubevirt2415%
  • github.com/kubernetes/kubernetes2214%
  • github.com/cloudnative-pg/cloudnative-pg2113%
  • k8s.io/kubernetes2113%

siblings

More from k8s.io/apimachinery/pkg/api/meta

The other most-called functions in this package. See all →