Patrick Ohly 4e28a08da3 client-go: call out WithContext inconsistency ...

This raises awareness so that developers hopefully get it right without having to
learn about it from compile errors. It also explains that creating a PR to
fix the naming is not desired.

Kubernetes-commit: f40892f4813f29fc305d59073d2464a1fd7d6fe5

2025-05-08 14:29:21 +02:00

..

auth

staging: fix "go vet" issues

2023-02-28 21:22:40 +01:00

cache

client-go: call out WithContext inconsistency

2025-05-08 14:29:21 +02:00

clientcmd

Deprecate kubeconfig's preference field in favor of kuberc

2025-05-13 13:39:13 +02:00

events

events: ensure the name is valid

2025-02-20 09:13:56 +00:00

internal/events

k8s.io/client-go/tools: support context for event recording

2023-09-18 09:13:22 +02:00

leaderelection

feat: Allow leases to have custom labels set when a new holder has the lease

2025-05-06 10:43:05 -07:00

metrics

client-go: add DNS resolver latency metrics (#115357)

2023-06-28 22:56:45 +02:00

pager

Add WithAlloc interface and stub implementations with base benchmarks

2023-05-27 17:57:35 -04:00

portforward

Fix test cases that may potentially cause a panic.

2025-03-11 17:41:37 +08:00

record

events: ensure the name is valid

2025-02-20 09:13:56 +00:00

reference

Use https links for k8s KEPs, issues, PRs, etc

2022-09-23 16:13:22 -04:00

remotecommand

client-go remotecommand: avoid "unexpected error" log when there is no error

2025-05-07 14:51:18 +02:00

watch

client-go watch: NewIndexerInformerWatcherWithContext -> WithLogger

2025-01-31 10:18:04 +01:00