Skip to content

Issues: kubernetes/client-go

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

23 Open 1,124 Closed
23 Open 1,124 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Argo controller manager - controller runtime log error stack
#1406 opened Feb 12, 2025 by pavan302-git
Leader election acquire loop should fail if the cluster is not reachable.
#1404 opened Feb 4, 2025 by sarthakkothari
LeaderElection NewFromKubeconfig support "Functional Options" pattern
#1403 opened Jan 26, 2025 by ivankatliarchuk
applyconfigurations: Generate conversions to original API objects
#1402 opened Jan 21, 2025 by mmonaco
client-go do not cache apis which can get from /apis ， but actually do not support
#1401 opened Jan 21, 2025 by WeiYongqiang55
1
fake client gives error using CreateToken operation for ServiceAccounts
#1396 opened Dec 23, 2024 by gdasson
fakeDynamicClient cannot filter resources using FieldSelector
#1393 opened Dec 11, 2024 by chinazj
1
Docs: Examples for how to use dynamic.DynamicClient
#1392 opened Dec 3, 2024 by guettli
Add an example on how to use SSA lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1386 opened Nov 6, 2024 by guettli
1
Add simple ResourceVersion tracking in fake.Clientset lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1385 opened Oct 30, 2024 by stippi2
1
client-go bind method reliable？ lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1382 opened Oct 24, 2024 by zj619
2
Retry watcher SSE or Http streaming? lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1374 opened Aug 29, 2024 by shubhanshusingh
3
Clientgo StreamWatcher is consuming high memory in high pod churn case help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
#1324 opened Dec 20, 2023 by kuldeepsolanki04
3
Add context to "Watch failed" lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1321 opened Dec 6, 2023 by jsoref
9
Events for cluster scoped CRs
#1262 opened May 29, 2023 by andreaskaris
14
namespace defaults to in-cluster namespace when run with explicit KUBECONFIG
#1241 opened Mar 29, 2023 by hojerst
14
Pluralization discrepancy in UnsafeGuessKindToResource still exists lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1082 opened Apr 7, 2022 by Limorerez
1
23
third_party isn't populated correctly lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#393 opened Apr 3, 2018 by bgrant0607
2
How to reinitialize client? lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
#342 opened Dec 8, 2017 by r7vme
3
Document where to use versioned struct and where not lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#289 opened Sep 6, 2017 by discordianfish
8
client-go needs backwards compatibility test lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#234 opened Jul 6, 2017 by caesarxuchao
23
Add examples of how a simple list and watch is built using client-go lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#161 opened Mar 30, 2017 by krmayankk
2
AddAfter should be able to cancel previous enqueues of the same key kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#131 opened Feb 25, 2017 by 0xmichalis
1
7
ProTip! Type g i on any issue or pull request to go back to the issue listing page.