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.

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

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

Issues list

Add an example on how to use SSA
#1386 opened Nov 6, 2024 by guettli
client-go bind method reliable?
#1382 opened Oct 24, 2024 by zj619
High memory when informer error occurs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1377 opened Sep 20, 2024 by zhulinwei
EventRecorder comment contradicts with Event field comment lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1375 opened Sep 13, 2024 by npinaeva
ServerResourcesForGroupVersion accepts a context lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1370 opened Jul 29, 2024 by rh-hemartin
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
Add context to "Watch failed"
#1321 opened Dec 6, 2023 by jsoref
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
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
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
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
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
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
ProTip! What’s not been updated in a month: updated:<2024-11-23.