-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Client library support for kubernetes 1.16 #1070
Comments
Please track #1052. Unfortunately, some of our core members are unavailable right now, so I cannot give you an exact time line. |
Thank you.
…On Tue, Feb 4, 2020 at 12:12 PM Xianglong Wang ***@***.***> wrote:
Please track #1052
<#1052>. Unfortunately,
some of our core members are unavailable right now, so I cannot give you an
exact time line.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1070?email_source=notifications&email_token=AK4V6EPULOTILHB43MGRXKTRBGOWPA5CNFSM4KPYDRBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKYNYAI#issuecomment-582016001>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK4V6EMPXRCSJLGZDNO4B3LRBGOWPANCNFSM4KPYDRBA>
.
--
Swapna
|
We are also waiting for 1.16 support. |
Same here, awaiting support for 1.16 🙏 |
Yes please track #1052 and #1088. Currently we are focusing on cutting 11.0.0 release. We will focus on 12.0.0a1 release once 11.0.0 is cut. /assign @scottilee |
@roycaihw: GitHub didn't allow me to assign the following users: scottilee. Note that only kubernetes-client members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
/assign |
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. |
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. |
/remove-lifecycle rotten |
@palnabarun When is the official release of 12.0.0 planned for? |
Alternatively, is there any reason to expect big changes from the beta to the full 12.0 release? If the beta is probably pretty close to release quality I might go ahead with using it for now. |
@gabrielcalderon @jheiss -- The stable release is due with this PR -> #1280 :) @jheiss -- The beta version is almost near to stable quality. The Kubernetes API doesn't change across Alpha/Beta/Stable client releases. |
v12.0 is released for k8s API 1.16.15 so this should be closed? (Hooray!, BTW)
|
Python Client for Kubernetes 1.16 has been released. :) /close |
@palnabarun: 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. |
We are upgrading platform with kubernetes 1.16. As per compatibility matrix current python client only supports until kubernetes 1.15 only. May I know the timeline when new version of python client library available to support 1.16.
The text was updated successfully, but these errors were encountered: