-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Kubernetes Version Compatibility #1170
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
Comments
Yes this client is lagging behind. We are catching up and doing the 12.0.0 release #1052 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
A proposal about cutting the following releases is in #1242. /remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
From the screenshot below shows that the supported Kubernetes version is up until 1.15 and the latest version now is 1.18.

May I know does this Python API Client library keep up-to-date with the Kubernetes version? Is there any drawback of using this API client library with Kubernetes version 1.18?
The text was updated successfully, but these errors were encountered: