Fly Changelog 1st May 2020

Summary

Fly’s 1 May 2020 changelog records enhancements to flyctl, a new Open Source page, and a revised load-balancing allocation algorithm. Version 0.0.117 added flyctl auth docker, allowing deployments of images directly to Fly by adding registry.fly.io to Docker’s authenticated registries, and introduced --image-label for selecting a specific image label at deployment time. The release also increased the timeout at the end of deployment monitoring to prevent erroneous “No Deployment” messages and changed deploy version negotiation to resolve API compatibility errors. For global applications with large numbers of instances, the new algorithm directs each incoming connection to an instance from the closest least-loaded service among three randomly selected healthy services in the app’s three nearest regions.

Takeaways

1. 1

   flyctl auth docker adds registry.fly.io to Docker’s authenticated registries so users can deploy images directly to Fly.

2. 2

   The new --image-label option lets flyctl deploy request a specific image label at deployment time.

3. 3

   The load balancer randomly selects healthy services from the three nearest regions, then routes connections to an instance from the closest least-loaded service.