API route to get geolocation information about an IP or a list of IPs. link
The termination grace period is now customizable within the settings of an app version. Increasing it lets you gracefully terminate your application before the container is fully killed.
Best practices CICD guide to help integrate Edgegap in your development pipelines. link
Fleet manager: the Deployment Scaler has been removed and replaced by the Fleet Manager. You can now create your fleets, policies, and filters which will automatically scale your Sessions at specific sites according to your configuration. Documentation
Container image validation when updating an application version.
The deployment's FQDN will no longer include the application name. It was sometime causing issues in the FQDN creation process.
From now on, it will only have the deployment's request ID.
Bug where the application versions errors were not cleaned correctly on an update, making our caching system disable cache for these versions needlessly.
Bug where an error was returned when requesting deployment metrics via the API too soon in the deployment lifecycle.
Bug when creating an application where the API was requesting optional parameters when using the "verify_image" option.
Bug with the container registry creating duplicate application versions when pushing the same tag multiple times.
Deployment timeline now available from the "Platform Info" tab on the deployment details page. This visual guide will make it easier to understand and improve each step of a deployment.
A warning message will now be shown on the deployment page when deploying using a reserved IP (e.g. 0.0.0.0). Since the geolocation cannot be determined in such a case, the default location of this player will be at lat/long 0.0.
Improvement in the Edge locations lifecycle management.
Edgegap Container Registry: Push and update your container images directly to the fully integrated Edgegap Container Registry for a simple version management experience (link).
You can now exclude region, city, country, etc from your deployment request.
You can now validate the container image for an application version to ensure that we can pull it from your selected registry. Available from the API and the dashboard.
You can now download a preconfigured TOML file for our CLI directly on the app version detail page.
You can now access the container logs of past deployments from the deployment history in the dashboard if you have setup an Endpoint Storage S3 bucket for your account.
You can now request telemetry for a list of IPs on existing deployments. (Documentation coming soon)
We added a new feature that allows you to store your container logs automatically to S3 type storage. You can follow our doc to enable it on your apps. link.
You can now create your Matchmaker directly in the Arbitrium Dashboard. You can follow the documentation under the Arbitrium Open Match.
SDK generator in Dashboard
Increased integration between your game server and Arbitrium, you can now generate the SDK from our Dashboard.
Protection of your deployment is automatically done.
If enabled in your application configuration, Arbitrium will protect your deployment. It will be reached ONLY from IP that you allowed.
Organization support in Dashboard.
We have the support of Organizations built into your Dashboard. Invite your coworker to the Organization, then hop in and out to leverage the same account.
Deployment context in the container
We added more information in your container. When you need to have scripts in your container to display information on the location, see the documentation to get more information on this feature.
Session-based deployment
We support matches that players are getting in and out of at any given time. We will add the players in the session that is in the best location for your players.
The horizontal Deployment Session tool will make sure you always have sessions ready to onboard new players.
Added the option to deploy to a specific location without taking telemetry data into account.
Added a “lock deployment” option if you need to have a deployment remain active. As long as a deployment is locked, the deployment cannot be killed by any requests.
Added access to more information inside our BigData repository directly from the Dashboard.
Added support for returning information to your matchmaker using a webhook.
Added the ability to create tags on your deployments to identify them more easily.