From 324d067b8a63f45f42876064e27ca9bb50532651 Mon Sep 17 00:00:00 2001 From: Robert Bailey Date: Mon, 5 Apr 2021 21:05:03 +0000 Subject: [PATCH] Update the website to use simple-game-server version 0.3. --- site/config.toml | 2 +- site/content/en/docs/Guides/local-game-server.md | 2 +- site/content/en/docs/Guides/troubleshooting.md | 10 +++++----- site/content/en/docs/Reference/fleet.md | 2 +- site/content/en/docs/Reference/gameserver.md | 6 +++--- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/site/config.toml b/site/config.toml index 0bbf3f01ec..096a9532c0 100644 --- a/site/config.toml +++ b/site/config.toml @@ -96,7 +96,7 @@ dev_aks_minor_supported_k8s = "14" dev_minikube_minor_supported_k8s = "15" # example tag -example_image_tag = "gcr.io/agones-images/simple-game-server:0.2" +example_image_tag = "gcr.io/agones-images/simple-game-server:0.3" # User interface configuration [params.ui] diff --git a/site/content/en/docs/Guides/local-game-server.md b/site/content/en/docs/Guides/local-game-server.md index 0bc57a31f3..807a21a864 100644 --- a/site/content/en/docs/Guides/local-game-server.md +++ b/site/content/en/docs/Guides/local-game-server.md @@ -32,7 +32,7 @@ spec: spec: containers: - name: simple-game-server - image: gcr.io/agones-images/simple-game-server:0.2 + image: {{< example-image >}} ``` Once you save this to a file make sure you have `kubectl` configured to point to your Agones cluster and then run `kubectl apply -f dev-gameserver.yaml`. This will register your server with Agones. diff --git a/site/content/en/docs/Guides/troubleshooting.md b/site/content/en/docs/Guides/troubleshooting.md index 34915c2e38..6d70214b25 100644 --- a/site/content/en/docs/Guides/troubleshooting.md +++ b/site/content/en/docs/Guides/troubleshooting.md @@ -83,7 +83,7 @@ Spec: Creation Timestamp: Spec: Containers: - Image: gcr.io/agones-images/simple-game-server:0.2 + Image: {{< example-image >}} Name: simple-game-server Resources: Limits: @@ -114,7 +114,7 @@ Events: The backing Pod has the same name as the `GameServer` - so it's also worth looking at the details and events for the Pod to see if there are any issues there, such as restarts due to binary crashes etc. -For example, you can see the restart count on the gcr.io/agones-images/simple-game-server:0.2 container +For example, you can see the restart count on the {{< example-image >}} container is set to `1`, due to the game server binary crash ``` @@ -136,7 +136,7 @@ Controlled By: GameServer/simple-game-server-zqppv Containers: simple-game-server: Container ID: docker://69eacd03cc89b0636b78abe47926b02183ba84d18fa20649ca443f5232511661 - Image: gcr.io/agones-images/simple-game-server:0.2 + Image: {{< example-image >}} Image ID: docker-pullable://gcr.io/agones-images/simple-game-server@sha256:6a60eff5e68b88b5ce75ae98082d79cff36cda411a090f3495760e5c3b6c3575 Port: 7654/UDP Host Port: 7058/UDP @@ -205,7 +205,7 @@ Events: Normal Created 2m28s kubelet, gke-test-cluster-default-590db5e4-4s6r Created container Normal Created 114s (x2 over 2m31s) kubelet, gke-test-cluster-default-590db5e4-4s6r Created container Normal Started 114s (x2 over 2m31s) kubelet, gke-test-cluster-default-590db5e4-4s6r Started container - Normal Pulled 114s (x2 over 2m31s) kubelet, gke-test-cluster-default-590db5e4-4s6r Container image "gcr.io/agones-images/simple-game-server:0.2" already present on machine + Normal Pulled 114s (x2 over 2m31s) kubelet, gke-test-cluster-default-590db5e4-4s6r Container image "{{< example-image >}}" already present on machine ``` Finally, you can also get the logs of your `GameServer` `Pod` as well via `kubectl logs -c `, for example: @@ -238,7 +238,7 @@ root@c9a845c474c2:/go/src/agones.dev/agones# kubectl get events | grep simple-ga 2m47s Normal Creating gameserver/simple-game-server-v992s-jwpx2 Pod simple-game-server-v992s-jwpx2 created 2m47s Normal Scheduled pod/simple-game-server-v992s-jwpx2 Successfully assigned default/simple-game-server-v992s-jwpx2 to gke-test-cluster-default-77e7f57d-j1mp 2m47s Normal Scheduled gameserver/simple-game-server-v992s-jwpx2 Address and port populated -2m46s Normal Pulled pod/simple-game-server-v992s-jwpx2 Container image "gcr.io/agones-images/simple-game-server:0.2" already present on machine +2m46s Normal Pulled pod/simple-game-server-v992s-jwpx2 Container image "{{< example-image >}}" already present on machine 2m46s Normal Created pod/simple-game-server-v992s-jwpx2 Created container simple-game-server 2m45s Normal Started pod/simple-game-server-v992s-jwpx2 Started container simple-game-server 2m45s Normal Pulled pod/simple-game-server-v992s-jwpx2 Container image "gcr.io/agones-images/agones-sdk:1.7.0" already present on machine diff --git a/site/content/en/docs/Reference/fleet.md b/site/content/en/docs/Reference/fleet.md index c8b7ac1883..a5c041e8ac 100644 --- a/site/content/en/docs/Reference/fleet.md +++ b/site/content/en/docs/Reference/fleet.md @@ -67,7 +67,7 @@ spec: spec: containers: - name: simple-game-server - image: gcr.io/agones-images/simple-game-server:0.2 + image: {{< example-image >}} ``` Since Agones defines a new diff --git a/site/content/en/docs/Reference/gameserver.md b/site/content/en/docs/Reference/gameserver.md index 4b2862a645..672aee7e06 100644 --- a/site/content/en/docs/Reference/gameserver.md +++ b/site/content/en/docs/Reference/gameserver.md @@ -12,7 +12,7 @@ A full GameServer specification is available below and in the {{< ghlink href="e ```yaml apiVersion: "agones.dev/v1" kind: GameServer -# GameServer Metadata +# GameServer Metadata # {{< k8s-api href="#objectmeta-v1-meta" >}} metadata: # generateName: "gds-example" # generate a unique name, with the given prefix @@ -87,13 +87,13 @@ spec: spec: containers: - name: simple-game-server - image: gcr.io/agones-images/simple-game-server:0.2 + image: {{< example-image >}} imagePullPolicy: Always ``` Since Agones defines a new [Custom Resources Definition (CRD)](https://kubernetes.io/docs/concepts/api-extension/custom-resources/) we can define a new resource using the kind `GameServer` with the custom group `agones.dev` and API version `v1`. -You can use the metadata field to target a specific [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) +You can use the metadata field to target a specific [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) but also attach specific [annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) and [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) to your resource. This is a very common pattern in the Kubernetes ecosystem. The length of the `name` field of the Gameserver should not exceed 63 characters.