Release 0.6.0 updates.

Author: markmandel

CHANGELOG.md

@@ -1,6 +1,14 @@
 # Changelog
 
-## [v0.6.0-rc](https://github.com/GoogleCloudPlatform/agones/tree/v0.6.0-rc) (2018-11-20)
+## [v0.6.0](https://github.com/GoogleCloudPlatform/agones/tree/v0.6.0) (2018-11-28)
+
+[Full Changelog](https://github.com/GoogleCloudPlatform/agones/compare/v0.6.0-rc...v0.6.0)
+
+**Closed issues:**
+
+- Release 0.6.0.rc [\#424](https://github.com/GoogleCloudPlatform/agones/issues/424)
+
+## [v0.6.0-rc](https://github.com/GoogleCloudPlatform/agones/tree/v0.6.0-rc) (2018-11-21)
 
 [Full Changelog](https://github.com/GoogleCloudPlatform/agones/compare/v0.5.0...v0.6.0-rc)
 
@@ -33,6 +41,7 @@
 
 **Merged pull requests:**
 
+- Release 0.6.0-rc [\#425](https://github.com/GoogleCloudPlatform/agones/pull/425) ([markmandel](https://github.com/markmandel))
 - More stringent linting rules \(and update linter\) [\#417](https://github.com/GoogleCloudPlatform/agones/pull/417) ([markmandel](https://github.com/markmandel))
 - FleetAutoscaler can be targeted at Non Existent Fleets [\#416](https://github.com/GoogleCloudPlatform/agones/pull/416) ([markmandel](https://github.com/markmandel))
 - Adding colour to the linter, because colours are pretty. [\#400](https://github.com/GoogleCloudPlatform/agones/pull/400) ([markmandel](https://github.com/markmandel))

docs/fleet_spec.md

@@ -54,7 +54,7 @@ This is a very common pattern in the Kubernetes ecosystem.
 The `spec` field is the actual `Fleet` specification and it is composed as follow:
 
 - `replicas` is the number of `GameServers` to keep Ready or Allocated in this Fleet
-- `scheduling`(⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️) defines how GameServers are organised across the cluster. Currently only affects Allocation, but will expand
+- `scheduling` defines how GameServers are organised across the cluster. Currently only affects Allocation, but will expand
                  in future releases. Options include:
                  "Packed" (default) is aimed at dynamic Kubernetes clusters, such as cloud providers, wherein we want to bin pack
                  resources. "Distributed" is aimed at static Kubernetes clusters, wherein we want to distribute resources across the entire

docs/gameserver_spec.md

@@ -2,7 +2,7 @@
 
 Like any other Kubernetes resource you describe a GameServer's desired state via a specification written in YAML or JSON to the Kubernetes API. The Agones controller will then change the actual state to the desired state.
 
-A full GameServer specification is available below and in the [example folder](https://github.com/GoogleCloudPlatform/agones/blob/release-0.5.0/examples/gameserver.yaml) for reference :
+A full GameServer specification is available below and in the [example folder](https://github.com/GoogleCloudPlatform/agones/blob/release-0.6.0/examples/gameserver.yaml) for reference :
 
 ```
 apiVersion: "stable.agones.dev/v1alpha1"

docs/governance/templates/release_issue.md

@@ -29,8 +29,8 @@ and copy it into a release issue. Fill in relevent values, found inside {}
   - [ ] Attach all assets found in the `release` folder to the release.
 - [ ] Send an email to the [mailing list][list] with the release details (copy-paste the github release)
 - [ ] If full release, then increment the `base_version` in [`build/Makefile`][build-makefile]
-- [ ] Ensure the [helm `tag` value][values] is set to the next version (should be the {version} if a full release, {version}-rc if release candidate)
-- [ ] Ensure the [helm `Chart` version values][chart] is set to the next version (should be the {version} if a full release, {version}-rc if release candidate)
+- [ ] Ensure the [helm `tag` value][values] is set to the next version (should be the {version}+0.1 if a full release, {version}+0.1-rc if release candidate)
+- [ ] Ensure the [helm `Chart` version values][chart] is set to the next version (should be the {version}+0.1 if a full release, {version}+0.1-rc if release candidate)
 - [ ] Run `make gen-install`
 - [ ] Create PR with these changes, and merge them with approval
 - [ ] Close this issue.

docs/limiting_resources.md

@@ -45,8 +45,6 @@ If you do not set a limit or request, the default is set my Kubernetes at a 100m
 
 ## SDK GameServer sidecar
 
-⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️
-
 You may also want to tweak the CPU request or limits on the SDK `GameServer` sidecar process that spins up alongside
 each game server container.
 

docs/scheduling_autoscaling.md

@@ -1,7 +1,5 @@
 # Scheduling and Autoscaling
 
-⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️
-
 > Autoscaling is currently ongoing work within Agones. The work you see here is just the beginning.
 
 Table of Contents

install/README.md

@@ -288,11 +288,11 @@ This will install Agones in your cluster.
 ## Install with YAML
 
 We can install Agones to the cluster using the
-[install.yaml](https://github.com/GoogleCloudPlatform/agones/blob/release-0.5.0/install/yaml/install.yaml) file.
+[install.yaml](https://github.com/GoogleCloudPlatform/agones/blob/release-0.6.0/install/yaml/install.yaml) file.
 
 ```bash
 kubectl create namespace agones-system
-kubectl apply -f https://github.com/GoogleCloudPlatform/agones/raw/release-0.5.0/install/yaml/install.yaml
+kubectl apply -f https://github.com/GoogleCloudPlatform/agones/raw/release-0.6.0/install/yaml/install.yaml
 ```
 
 You can also find the install.yaml in the latest `agones-install` zip from the [releases](https://github.com/GoogleCloudPlatform/agones/releases) archive.

install/helm/README.md

@@ -92,8 +92,8 @@ The following tables lists the configurable parameters of the Agones chart and t
 | `agones.image.controller.pullPolicy`                | Image pull policy for the controller                                                            | `IfNotPresent`         |
 | `agones.image.controller.pullSecret`                | Image pull secret for the controller                                                            | ``                     |
 | `agones.image.sdk.name`                             | Image name for the sdk                                                                          | `agones-sdk`           |
-| `agones.image.sdk.cpuRequest`                       | (⚠️ release candidate feature ⚠️) the [cpu request][constraints] for sdk server container              | `30m`                  |
-| `agones.image.sdk.cpuLimit`                         | (⚠️ release candidate feature ⚠️) the [cpu limit][constraints] for the sdk server container            | `0` (none)             |
+| `agones.image.sdk.cpuRequest`                       | The [cpu request][constraints] for sdk server container                                         | `30m`                  |
+| `agones.image.sdk.cpuLimit`                         | The [cpu limit][constraints] for the sdk server container                                       | `0` (none)             |
 | `agones.image.sdk.alwaysPull`                       | Tells if the sdk image should always be pulled                                                  | `false`                |
 | `agones.controller.healthCheck.http.port`           | Port to use for liveness probe service                                                          | `8080`                 |
 | `agones.controller.healthCheck.initialDelaySeconds` | Initial delay before performing the first probe (in seconds)                                    | `3`                    |

install/helm/agones/Chart.yaml

@@ -15,8 +15,8 @@
 # Declare variables to be passed into your templates.
 
 apiVersion: v1
-appVersion: "0.6.0-rc"
-version: 0.6.0-rc
+appVersion: "0.6.0"
+version: 0.6.0
 name: agones
 description: a library for hosting, running and scaling dedicated game servers on Kubernetes.
 keywords:

install/helm/agones/values.yaml

@@ -32,7 +32,7 @@ agones:
       timeoutSeconds: 1
   image:
     registry: gcr.io/agones-images
-    tag: 0.6.0-rc
+    tag: 0.6.0
     controller:
       name: agones-controller
       pullPolicy: IfNotPresent