-
Notifications
You must be signed in to change notification settings - Fork 828
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
Upgrade to Kubernetes 1.15 #1478
Comments
Added EKS to terraform list, since 1.15 is supported there. |
@heartrobotninja - do you want to do the client-go updates again this release cycle? |
I'll start working on the checklist this week. /assign |
Yeah, I will get started tomorrow.
…On Tue, Apr 21, 2020 at 11:56 AM Robert Bailey ***@***.***> wrote:
I'll start working on the checklist this week.
/assign
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABM5DZ6NB3GHBCNIOSTJ7OTRNXT6VANCNFSM4MJFCV7Q>
.
|
This time we also need to update |
I've updated the client but am running into some problems which look a lot like kubernetes/kubernetes#86666 (which seems to affect 1.16 and 1.17, but I am seeing this with 1.15.11) |
I've had namespaces get stuck because of finalisers on GameServer objects not yet being removed (often because of the Agones controller not existing). Is it akin to that, or are you getting some kind of error message @heartrobotninja ? |
Looks like the deployment scripts for the e2e tests have updated to 1.15 -- any reason I shouldn't upgrade the e2e cluster? |
I started doing some work on upgrading the client to 1.15 support, since I also had to update the script for generating the crd clients to make it work. https://github.com/markmandel/agones/tree/feature/1.15-client Unit tests all pass except for
First few e2e tests I've tried, all looks good, but this is the only blocking issue I've run into so far. @aLekSer any ideas on the fuzzing test? @heartrobotninja is this what you ran into before? |
In this PR https://github.com/kubernetes/kubernetes/pull/78309/files last
kubernetes/apimachinery@3610fc3 |
As a workaround, there is an option to use the code similar to what was used in Kubernetes 1.14:
instead of |
By the way with a new version there is a possibility to add Compatibility test, but need to add json files in
|
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on googleforgames#1478
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on googleforgames#1478
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on googleforgames#1478
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on googleforgames#1478
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on #1478
Just highlighting a risk -- if the plan was to get this in to the next release, RC is next Tuesday. |
Since we're moving to 1.16, should we close this ticket? |
Yep. I think that makes sense.
…On Tue, Jul 14, 2020, 10:15 AM Mark Mandel ***@***.***> wrote:
Since we're moving to 1.16, should we close this ticket?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABM5DZ6YZINXKS6YHAA57R3R3SHCDANCNFSM4MJFCV7Q>
.
|
Seems like we have consensus, I'll close this ticket then! |
This upgrade client-go, apimachinery, apiextensions-apiserver and related to support Kubernetes 1.15, as well as regenerated clients for our CRDs. Also included is a fix to gen-crd-client.sh such that it can now use Go modules, as otherwise it was failing to generate clients. Work on googleforgames#1478
Now that Amazon EKS Kubernetes Versions shows that Kubernetes 1.15 is now available on EKS, as per our impending policy change for which Kubernetes version to support, it's time to upgrade to Kubernetes 1.15.
List of items to do for upgrading to 1.15 (this is copied from the 1.14 issue and may need to be updated):
e2e-image/Dockerfile
The text was updated successfully, but these errors were encountered: