diff --git a/CHANGELOG.md b/CHANGELOG.md index f6863e4a11..b6e9dc5bb5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,17 @@ # Changelog +## [v0.7.0](https://github.com/GoogleCloudPlatform/agones/tree/v0.7.0) (2019-01-08) + +[Full Changelog](https://github.com/GoogleCloudPlatform/agones/compare/v0.7.0-rc...v0.7.0) + +**Closed issues:** + +- Release 0.7.0-rc [\#467](https://github.com/GoogleCloudPlatform/agones/issues/467) + +**Merged pull requests:** + +- Preparation for 0.7.0 [\#470](https://github.com/GoogleCloudPlatform/agones/pull/470) ([markmandel](https://github.com/markmandel)) + ## [v0.7.0-rc](https://github.com/GoogleCloudPlatform/agones/tree/v0.7.0-rc) (2019-01-02) [Full Changelog](https://github.com/GoogleCloudPlatform/agones/compare/v0.6.0...v0.7.0-rc) @@ -43,6 +55,7 @@ **Merged pull requests:** +- Release 0.7.0-rc [\#468](https://github.com/GoogleCloudPlatform/agones/pull/468) ([markmandel](https://github.com/markmandel)) - Move the README.md into /agones/ so it's in the Helm Chart [\#466](https://github.com/GoogleCloudPlatform/agones/pull/466) ([markmandel](https://github.com/markmandel)) - Convert to using Fluentdformatter [\#463](https://github.com/GoogleCloudPlatform/agones/pull/463) ([markmandel](https://github.com/markmandel)) - Upgrade minikube to K8s 1.11 [\#459](https://github.com/GoogleCloudPlatform/agones/pull/459) ([markmandel](https://github.com/markmandel)) diff --git a/docs/create_webhook_fleetautoscaler.md b/docs/create_webhook_fleetautoscaler.md index 655a79039b..d6af298b08 100644 --- a/docs/create_webhook_fleetautoscaler.md +++ b/docs/create_webhook_fleetautoscaler.md @@ -1,7 +1,5 @@ # Quickstart Create a Fleet Autoscaler with Webhook Policy -⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️ - This guide covers how you can create webhook fleet autoscaler policy. The main difference from the Buffer policy is that the logic on how many target replicas you need is delegated to a separate pod. This type of Autoscaler would send an HTTP request to the webhook endpoint every sync period (which is currently 30s) with a JSON body, and scale the target fleet based on the data that is returned. diff --git a/docs/gameserver_spec.md b/docs/gameserver_spec.md index 9499210872..363b454cb0 100644 --- a/docs/gameserver_spec.md +++ b/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.6.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.7.0/examples/gameserver.yaml) for reference : ``` apiVersion: "stable.agones.dev/v1alpha1" diff --git a/docs/metrics.md b/docs/metrics.md index 4508f88c19..58764e7f14 100644 --- a/docs/metrics.md +++ b/docs/metrics.md @@ -1,7 +1,5 @@ # Metrics -⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️ - Agones controller exposes metrics via [OpenCensus](https://opencensus.io/). OpenCensus is a single distribution of libraries that collect metrics and distributed traces from your services, we only use it for metrics but it will allow us to support multiple exporters in the future. We choose to start with Prometheus as this is the most popular with Kubernetes but it is also compatible with Stackdriver. diff --git a/docs/ping_service.md b/docs/ping_service.md index a6bd60bd47..a41c17d920 100644 --- a/docs/ping_service.md +++ b/docs/ping_service.md @@ -1,7 +1,5 @@ # Latency Testing with Multiple Clusters -⚠️⚠️⚠️ **This is currently a release candidate feature** ⚠️⚠️⚠️ - When running multiple Agones clusters around the world, you may need to have clients determine which cluster to connect to based on latency. diff --git a/install/README.md b/install/README.md index cba69af7f2..3ee479313f 100644 --- a/install/README.md +++ b/install/README.md @@ -286,11 +286,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.6.0/install/yaml/install.yaml) file. +[install.yaml](https://github.com/GoogleCloudPlatform/agones/blob/release-0.7.0/install/yaml/install.yaml) file. ```bash kubectl create namespace agones-system -kubectl apply -f https://github.com/GoogleCloudPlatform/agones/raw/release-0.6.0/install/yaml/install.yaml +kubectl apply -f https://github.com/GoogleCloudPlatform/agones/raw/release-0.7.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. diff --git a/install/helm/agones/README.md b/install/helm/agones/README.md index 95c23cdd2b..4602c4aac7 100644 --- a/install/helm/agones/README.md +++ b/install/helm/agones/README.md @@ -99,8 +99,8 @@ The following tables lists the configurable parameters of the Agones chart and t | `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.image.ping.name` | ( ⚠️ release candidate feature ⚠️ ) Image name for the ping service | `agones-ping` | -| `agones.image.ping.pullPolicy` | ( ⚠️ release candidate feature ⚠️ ) Image pull policy for the ping service | `IfNotPresent` | +| `agones.image.ping.name` | Image name for the ping service | `agones-ping` | +| `agones.image.ping.pullPolicy` | Image pull policy for the ping service | `IfNotPresent` | | `agones.controller.http.port` | Port to use for liveness probe service and metrics | `8080` | | `agones.controller.healthCheck.initialDelaySeconds` | Initial delay before performing the first probe (in seconds) | `3` | | `agones.controller.healthCheck.periodSeconds` | Seconds between every liveness probe (in seconds) | `3` | @@ -108,20 +108,20 @@ The following tables lists the configurable parameters of the Agones chart and t | `agones.controller.healthCheck.timeoutSeconds` | Number of seconds after which the probe times out (in seconds) | `1` | | `agones.controller.resources` | Controller resource requests/limit | `{}` | | `agones.controller.generateTLS` | Set to true to generate TLS certificates or false to provide your own certificates in `certs/*` | `true` | -| `agones.ping.install` | ( ⚠️ release candidate feature ⚠️ ) Whether to install the [ping service][ping] | `true` | -| `agones.ping.replicas` | ( ⚠️ release candidate feature ⚠️ ) The number of replicas to run in the deployment | `2` | -| `agones.ping.http.expose` | ( ⚠️ release candidate feature ⚠️ ) Expose the http ping service via a Service | `true` | -| `agones.ping.http.response` | ( ⚠️ release candidate feature ⚠️ ) The string response returned from the http service | `ok` | -| `agones.ping.http.port` | ( ⚠️ release candidate feature ⚠️ ) The port to expose on the service | `80` | -| `agones.ping.http.serviceType` | ( ⚠️ release candidate feature ⚠️ ) The [Service Type][service] of the HTTP Service | `LoadBalancer` | -| `agones.ping.udp.expose` | ( ⚠️ release candidate feature ⚠️ ) Expose the udp ping service via a Service | `true` | -| `agones.ping.udp.rateLimit` | ( ⚠️ release candidate feature ⚠️ ) Number of UDP packets the ping service handles per instance, per second, per sender | `20` | -| `agones.ping.udp.port` | ( ⚠️ release candidate feature ⚠️ ) The port to expose on the service | `80` | -| `agones.ping.udp.serviceType` | ( ⚠️ release candidate feature ⚠️ ) The [Service Type][service] of the UDP Service | `LoadBalancer` | -| `agones.ping.healthCheck.initialDelaySeconds` | ( ⚠️ release candidate feature ⚠️ ) Initial delay before performing the first probe (in seconds) | `3` | -| `agones.ping.healthCheck.periodSeconds` | ( ⚠️ release candidate feature ⚠️ ) Seconds between every liveness probe (in seconds) | `3` | -| `agones.ping.healthCheck.failureThreshold` | ( ⚠️ release candidate feature ⚠️ ) Number of times before giving up (in seconds) | `3` | -| `agones.ping.healthCheck.timeoutSeconds` | ( ⚠️ release candidate feature ⚠️ ) Number of seconds after which the probe times out (in seconds) | `1` | +| `agones.ping.install` | Whether to install the [ping service][ping] | `true` | +| `agones.ping.replicas` | The number of replicas to run in the deployment | `2` | +| `agones.ping.http.expose` | Expose the http ping service via a Service | `true` | +| `agones.ping.http.response` | The string response returned from the http service | `ok` | +| `agones.ping.http.port` | The port to expose on the service | `80` | +| `agones.ping.http.serviceType` | The [Service Type][service] of the HTTP Service | `LoadBalancer` | +| `agones.ping.udp.expose` | Expose the udp ping service via a Service | `true` | +| `agones.ping.udp.rateLimit` | Number of UDP packets the ping service handles per instance, per second, per sender | `20` | +| `agones.ping.udp.port` | The port to expose on the service | `80` | +| `agones.ping.udp.serviceType` | The [Service Type][service] of the UDP Service | `LoadBalancer` | +| `agones.ping.healthCheck.initialDelaySeconds` | Initial delay before performing the first probe (in seconds) | `3` | +| `agones.ping.healthCheck.periodSeconds` | Seconds between every liveness probe (in seconds) | `3` | +| `agones.ping.healthCheck.failureThreshold` | Number of times before giving up (in seconds) | `3` | +| `agones.ping.healthCheck.timeoutSeconds` | Number of seconds after which the probe times out (in seconds) | `1` | | `gameservers.namespaces` | a list of namespaces you are planning to use to deploy game servers | `["default"]` | | `gameservers.minPort` | Minimum port to use for dynamic port allocation | `7000` | | `gameservers.maxPort` | Maximum port to use for dynamic port allocation | `8000` |