-
Notifications
You must be signed in to change notification settings - Fork 817
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
Update to Kubernetes 1.11 #447
Update to Kubernetes 1.11 #447
Conversation
Now we have >= 1.11 support across cloud providers, we can finally update client-go to provide extra features. This updated client-go to 8.0.0 this includes Status API on the clients so we can take advantage of it - which should ideally give us a performance boost. *Please note:* this will mean that our required Kubernetes version will now be 1.11+, I think this is acceptable now it has penetration across cloud providers, but feedback appreciated. Also took the opportunity to upgrade logrus, errors, testify as well.
Build Succeeded 👏 Build Id: 7c729e42-13f3-449e-b97d-c89c6de24a78 The following development artifacts have been built, and will exist for the next 30 days:
To install this version:
|
Things the move to 1.11 will make possible across the board:
|
LGTM! |
Build Succeeded 👏 Build Id: 1b6fd29e-9be0-481b-8f5a-d9a66fb9e7be The following development artifacts have been built, and will exist for the next 30 days:
To install this version:
|
1 similar comment
Build Succeeded 👏 Build Id: 1b6fd29e-9be0-481b-8f5a-d9a66fb9e7be The following development artifacts have been built, and will exist for the next 30 days:
To install this version:
|
Now we have >= 1.11 support across cloud providers, we can finally update client-go to provide extra features.
This updated client-go to 8.0.0 this includes Status API on the clients so we can take advantage of it - which should ideally give us a performance boost.
Please note: this will mean that our required Kubernetes version will now be 1.11+, I think this is acceptable now it has penetration across cloud providers, but feedback appreciated.
Also took the opportunity to upgrade logrus, errors, testify as well.
This makes #329 possible.