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

25 Open 1,109 Closed
25 Open 1,109 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

Question about version compatibility of go-client with k8s api server
#1387 opened Nov 7, 2024 by kafkaphoenix
Add an example on how to use SSA
#1386 opened Nov 6, 2024 by guettli
Add simple ResourceVersion tracking in fake.Clientset
#1385 opened Oct 30, 2024 by stippi2
client-go bind method reliable？
#1382 opened Oct 24, 2024 by zj619
ManagedFieldsEntryApplyConfiguration Not Part of ObjectMetaApplyConfiguration
#1378 opened Sep 24, 2024 by brito-rafa
High memory when informer error occurs.
#1377 opened Sep 20, 2024 by zhulinwei
EventRecorder comment contradicts with Event field comment
#1375 opened Sep 13, 2024 by npinaeva
1
Retry watcher SSE or Http streaming?
#1374 opened Aug 29, 2024 by shubhanshusingh
1
ServerResourcesForGroupVersion accepts a context lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1370 opened Jul 29, 2024 by rh-hemartin
1
Compatibility clarification on upgrade lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1369 opened Jul 25, 2024 by jnlycklama
1
potential bug, get endpoints method lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1368 opened Jul 25, 2024 by yashjaind11
1
can not exec find cmd use remotecommand lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1367 opened Jul 17, 2024 by testwill
3
unable to expand resource shortcut for resource provided by extension apiserver lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1365 opened Jul 12, 2024 by Diaphteiros
2
[PANIC] shared_informer.go ; Using v0.24.2 client-go ; lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1364 opened Jul 3, 2024 by singhalkanika198
2
FieldSelector doesn't appear to be filtering properly lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1350 opened Apr 19, 2024 by jacobwolfaws
4
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"
#1321 opened Dec 6, 2023 by jsoref
8
namespace defaults to in-cluster namespace when run with explicit KUBECONFIG
#1241 opened Mar 29, 2023 by hojerst
12
Pluralization discrepancy in UnsafeGuessKindToResource still exists
#1082 opened Apr 7, 2022 by Limorerez
1
21
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! What’s not been updated in a month: updated:<2024-10-19.