Skip to content
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

Fix Installation Docs and example GS configuration #962

Merged
merged 3 commits into from
Jul 31, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions examples/gameserver.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ spec:
# - "Passthrough" dynamically sets the `containerPort` to the same value as the dynamically selected hostPort.
# This will mean that users will need to lookup what port has been opened through the server side SDK.
# port is available. When static is the policy specified, `hostPort` is required to be populated
portPolicy: Dynamic
portPolicy: Static
# the port that is being opened on the game server process
containerPort: 7654
# the port exposed on the host, only required when `portPolicy` is "Static". Overwritten when portPolicy is "Dynamic".
Expand Down Expand Up @@ -71,5 +71,5 @@ spec:
spec:
containers:
- name: example-server
image: gcr.io/agones/test-server:0.1
image: gcr.io/agones-images/udp-server:0.14
imagePullPolicy: Always
30 changes: 22 additions & 8 deletions site/content/en/docs/Installation/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ In this quickstart, we will create a Kubernetes cluster, and populate it with th
## Usage Requirements

- Kubernetes cluster version 1.11
- [Minikube](https://github.com/kubernetes/minikube), [Kind](https://github.com/kubernetes-sigs/kind), [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/),
- [Minikube](https://github.com/kubernetes/minikube), [Kind](https://github.com/kubernetes-sigs/kind), [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/),
[Azure Kubernetes Service](https://azure.microsoft.com/en-us/services/kubernetes-service/) and [Amazon EKS](https://aws.amazon.com/eks/) have been tested
- If you are creating and managing your own Kubernetes cluster, the
[MutatingAdmissionWebhook](https://kubernetes.io/docs/admin/admission-controllers/#mutatingadmissionwebhook-beta-in-19), and
Expand Down Expand Up @@ -243,7 +243,7 @@ Create your EKS instance using the [Getting Started Guide](https://docs.aws.amaz

### Ensure VPC CNI 1.2 is Running

EKS does not use the normal Kubernetes networking since it is [incompatible with Amazon VPC networking](https://www.contino.io/insights/kubernetes-is-hard-why-eks-makes-it-easier-for-network-and-security-architects).
EKS does not use the normal Kubernetes networking since it is [incompatible with Amazon VPC networking](https://www.contino.io/insights/kubernetes-is-hard-why-eks-makes-it-easier-for-network-and-security-architects).

In a console, run this command to get your current cni version

Expand Down Expand Up @@ -272,7 +272,7 @@ You can use either [Azure Cloud Shell](https://docs.microsoft.com/azure/cloud-sh

If you are using Azure CLI from your local shell, you need to login to your Azure account by executing the `az login` command and following the login procedure.

Here are the steps you need to follow to create a new AKS cluster (additional instructions and clarifications are listed [here](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough)):
Here are the steps you need to follow to create a new AKS cluster (additional instructions and clarifications are listed [here](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough)):

```bash
# Declare necessary variables, modify them according to your needs
Expand Down Expand Up @@ -378,14 +378,28 @@ To confirm Agones is up and running, run the following command:
kubectl describe --namespace agones-system pods
```

It should describe the single pod created in the `agones-system` namespace, with no error messages or status. The `Conditions` section should look like this:
It should describe six pods created in the `agones-system` namespace, with no error messages or status. All `Conditions` sections should look like this:

```
Conditions:
Type Status
Initialized True
Ready True
PodScheduled True
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
```

All this pods should be in a `RUNNING` state:
```bash
kubectl get pods --namespace agones-system

NAME READY STATUS RESTARTS AGE
agones-controller-79f6c59bdb-9swzz 1/1 Running 0 2m47s
agones-ping-8598d64bbd-gd6cg 1/1 Running 0 2m47s
agones-ping-8598d64bbd-tjpcx 1/1 Running 0 2m47s
gameserver-allocator-6bd4d456f9-bbj76 1/1 Running 0 2m48s
gameserver-allocator-6bd4d456f9-vlkhk 1/1 Running 0 2m48s
gameserver-allocator-6bd4d456f9-x7t9h 1/1 Running 0 2m48s
```

That's it! This creates the [Custom Resource Definitions][crds] that power Agones and allows us to define resources of type `GameServer`.
Expand Down