-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Support for kubernetes 1.18.+ #1153
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
@SockenSalat We are actively working on releasing 1.16 client: #1141. Support for 1.18 is planned and will come after that |
@roycaihw Great to hear, thank you. |
I'm not sure I understand why this is closed. Is it closed as in "wontfix" or is it closed as in "wontfix" till 1.16 and 1.17 are released ? Thanks for maintaining this project by the way. |
We have 1.18.+ cluster we would like to keep talking to with this python client (used in checkmk supervision). Any chances of getting it to work by using the release-12.0 branch ? https://github.com/kubernetes-client/python/tree/release-12.0 |
@arthurlogilab
I closed this Issue becaus it is stated that Support for 1.18 is planned. |
@SockenSalat Thanks for your response. On a number of open source project I am used to subscribing to an issue I am interested in to get updates on the completion of such a task. In the case of this project how can I do that ? Should I subscribe to the releases ? (in the case where I follow an issue I can help out in the review or by testing an associated pull request). Thanks for your clarifications. |
@arthurlogilab I just subscribed the releases for getting notified when to take a look again |
I have a probelm currently with a nagios plugin utilizing this client.
I'm not familar with python, but if I read the compatibility table correctly and take k8s Release notes into account, I get the impression that the API changes mentioned are the reason for my problem.
So my question is: are there any plans to support k8s in version 1.18?
The text was updated successfully, but these errors were encountered: