client-go
client-go copied to clipboard
Go client for Kubernetes.
We have recently uncovered an error in our [boskos](https://github.com/kubernetes-sigs/boskos) instance like the following: ``` E0710 21:02:45.211259 1 leaderelection.go:330] error retrieving resource lock ci/boskos-cleaner-leaderlock: leases.coordination.k8s.io "boskos-cleaner-leaderlock" is forbidden: User "system:serviceaccount:ci:boskos" cannot...
In various cases, Kubernetes administrators restrict users to see all cluster's namespaces. It would be beneficial to have a feature that lists all namespaces within a config's contexts, rather than...
Is there please a plan to support labeled Events in EventRecorder interface? Labels are the default filter objects for filtering in lists of k8s resources. It would be sufficient to...
when I deploy my program which aims to watch all k8s's deployment's cpu and memory on k8s,it shows the error : "unknown (get deployments.apps)" here are where my error happend...
After upgrading client-go from version 0.25.3 to 0.26.4, observed following issues related to informer ``` Event Manager service url: https://172.30.155.177:10666/api/v1/eventmanager/alerts E0703 09:30:03.973283 1 reflector.go:140] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:169: Failed to watch *unstructured.Unstructured: unknown...
Hello, I am opening this issue to discuss a potential misuse of `http.DefaultClient` in `rest.HTTPClientFor`. The function appears to make the assumption that `http.DefaultClient` will always use `http.DefaultTransport`, which may...
Where should events for cluster scoped CRs be created? Does it have to be the default namespace? If so, are there any plans to either add events for cluster scoped...
Hello all, I'm not sure if this is the right place, maybe there is a simple solution, but I have been struggling with this use case, so I'll post it...
Hi! I'm trying to get the client version programmatically, similar to the `kubectl version` command. I'm using the `Get()` method defined in the `k8s.io/client-go/pkg/version` package to get the client version....
At the moment, there is no option to avoid logging certain errors, which also prevents dependent repositories from operating on these errors in a way that would make more sense...