-
Notifications
You must be signed in to change notification settings - Fork 819
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 documentation for the 1.2 release to use Kubernetes 1.13. #1178
Update documentation for the 1.2 release to use Kubernetes 1.13. #1178
Conversation
Build Succeeded 👏 Build Id: 2284e25e-9b46-44c8-8ad7-5231f09796ea The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
I see your point from before - we can't have a central place, as we couldn't feature block the new version of Kubernetes. Sounds like find and replace it is! |
b38c9fe
to
0a80168
Compare
@aLekSer - are you able to test these instructions of EKS / AKS? |
Build Succeeded 👏 Build Id: 81789ae0-7b76-4b31-b728-31c645c55ba8 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Hello @roberthbailey I will test and let you know soon. |
|
||
# Create the AKS cluster - this might take some time. Type 'az aks create -h' to see all available options | ||
# The following command will create a single Node AKS cluster. Node size is Standard A1 v1 and Kubernetes version is 1.13.12. Plus, SSH keys will be generated for you, use --ssh-key-value to provide your values | ||
az aks create --resource-group $AKS_RESOURCE_GROUP --name $AKS_NAME --node-count 1 --generate-ssh-keys --node-vm-size Standard_A4_v2 --kubernetes-version 1.13.12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This command has executed fine for me, I was able to install agones afterwards using install.yaml.
At the end I have tested deployment with creating a simple-udp
fleet.
Running E2E tests right now, I expect that we should increase node-count to 4 as in GKE cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E2E tests are failing. For instance, here:
FAIL: TestPingHTTP (30.11s)
ping_test.go:50:
Error Trace: ping_test.go:50
Error: Expected nil, but got: &url.Error{Op:"Get", URL:"http://51.105.176.201:80", Err:(*net.OpError)(0xc00040a000)}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy to increase the node count to 4.
What is the IP address for that can't be fetched? Can you tell if it's because the cluster is too small and there are pending pods?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to test one more time, could be connectivity issue between PC running E2E tests and the cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I followed all instructions for AKS cluster, issues does not related to this change.
Something is missing in description on how to create UDP firewall for port range.
Therefore I think I would send a separate PR for the fix of docs to make E2E tests passing on both AKS and EKS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for testing this out @aLekSer!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've adjusted the AKS instructions to create a 4 node cluster instead of a 1 node cluster.
0a80168
to
23ded6c
Compare
Build Failed 😱 Build Id: 5e6874b5-8465-4fe0-b0bf-6031afb9340c To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
23ded6c
to
7fc61f9
Compare
Build Failed 😱 Build Id: cfd179a0-b76e-48b8-aa5e-281b0c7e9f68 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
7fc61f9
to
b5bdae5
Compare
Build Succeeded 👏 Build Id: 30b80b57-d9a0-4172-b930-57beaf64fa67 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Tested this PR on AWS EKS, it works fine. |
b5bdae5
to
1d95c71
Compare
@markmandel - @aLekSer tested this on EKS/AKS and I know I tested on GKE. It's been long enough that I can't remember if I tested on minikube / kind but I think I did. Might be worth one more pass and then we should get this merged. |
Build Failed 😱 Build Id: 3b9e9f28-03e6-461f-a4de-17c70c447919 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: 0653f809-2361-45e1-a1c2-a305ec86c563 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
1d95c71
to
dbffb33
Compare
Build Succeeded 👏 Build Id: dbe4f143-d07d-4212-9052-9c7b7b6da027 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Also update links from examples to Kubernetes 1.13 docs.
dbffb33
to
2334dec
Compare
I just went through the minikube instructions and verified that they work (and KIND isn't part of this PR -- it's in the developer docs but not part of the user facing website docs). I made one small fix -- the GKE and minikube sections somehow lost their link pointing users to continue to the installing agones section at the bottom of the page, so I've added that in. /hold cancel |
Build Succeeded 👏 Build Id: eaf75698-59e9-4742-a888-86e16e18e4c4 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…gleforgames#1178) Also update links from examples to Kubernetes 1.13 docs.
Also update links from examples to Kubernetes 1.13 docs.
Closes #1044
/hold
Adding a hold until we can test Kubernetes 1.13 on EKS & AKS.