$ the-wire · showcase
Minikube probes drivers in parallel, promo-tools signs promotion records
By RepoJournal · Filed · About Kubernetes · Composed from the cited sources · methodology
The day's only behavior changes landed in minikube's driver probing and the release tooling's promotion attestations; everything else is dependency and docs churn.
registry: Probe drivers in parallel with per-driver timeouts kubernetes/minikube
The registry path used to probe drivers one after another, so total probe time was the sum of every driver's timeout, up to 20 seconds in the worst case; it now probes them concurrently, capping elapsed time at the slowest single driver and keeping one hung driver from stalling the rest. Each driver keeps its own timeout rather than sharing a global budget.
Bump sigs.k8s.io/promo-tools/v4 from 4.5.1 to 4.6.0 kubernetes/release
The release tooling picks up promo-tools/v4 4.6.0, whose stated highlight is that "Promotion record attestations are signed and attached as OCI referrers". That changes the artifacts promotion records produce, so anything consuming promotion output downstream should account for the new referrers.
Merge pull request #4536 from kubernetes/dependabot/github_actions/actions-c35057482f kubernetes/release
Four GitHub Actions in the release repo move together in one grouped bump, alongside the promo-tools version change in the same merge window.
chore(deps): bump the golang-org group across 1 directory with 7 updates kubernetes/minikube
Minikube's golang.org/x group advances across seven modules, including x/crypto 0.56.0 to 0.57.0 and x/sys 0.47.0 to 0.48.0. Routine, but it touches the crypto and syscall layers minikube builds against.
Merge pull request #4381 from kubernetes/dependabot/go_modules/perfdash/github.com/aws/aws-sdk-go-v2/credentials-1.20.5 kubernetes/perf-tests
Quiet tail: perfdash dependency bumps (aws-sdk-go-v2 credentials and S3), a duplicate klog warning removed from the stop command, five zh-cn documentation syncs covering imagepolicy, kube-proxy, apiserver, scheduler config and node metrics, and a missing protocol fixed on the k8s.dev link in the events-team comms README.
