Skip to content

Issues: kubernetes-client/java

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

Clear current search query, filters, and sorts
8 Open 10 Closed
8 Open 10 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

Unable to interact with cluster through Teleport lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3242 opened Mar 22, 2024 by nicolas-goudry
14
TLSServerName is not taken into account lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3241 opened Mar 22, 2024 by nicolas-goudry
7
It's not possible to create a Pod, because of the default overhead value (empty map) in v20.0.0 lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#3076 opened Feb 14, 2024 by kvmw
25
ExecTest is flaky. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#2107 opened Jan 25, 2022 by brendandburns
1
10
Failed to generate spec from crd lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1254 opened Sep 10, 2020 by kinderyj
9
[Umbrella Issue] Many tests use Thread.sleep instead of synchronization primitives good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1223 opened Sep 3, 2020 by brendandburns
@yue9944882 @tmrpavan
14
Can't create K8sDeployment object because of null creationTimestamp or deletionTimestamp fields in yaml file lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#845 opened Dec 30, 2019 by ansh7jan
5
GCP authentication does not support refreshing tokens lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#290 opened Jun 19, 2018 by omerkarj
33
ProTip! no:milestone will show everything without a milestone.