-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Label
Projects
Milestones
Assignee
Sort
Issues list
Question about version compatibility of go-client with k8s api server
#1387
opened Nov 7, 2024 by
kafkaphoenix
ManagedFieldsEntryApplyConfiguration Not Part of ObjectMetaApplyConfiguration
#1378
opened Sep 24, 2024 by
brito-rafa
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
namespace defaults to in-cluster namespace when run with explicit
KUBECONFIG
#1241
opened Mar 29, 2023 by
hojerst
Pluralization discrepancy in UnsafeGuessKindToResource still exists
#1082
opened Apr 7, 2022 by
Limorerez
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!
Add no:assignee to see everything that’s not assigned.