Linking Version
Last updated
Was this helpful?
Last updated
Was this helpful?
To make your fleet work as effectively as possible, we recommend using the option in the application's version session config.
That way, when your deployment has no session in it for a certain amount of time (specified by the empty time to live), the system will automatically delete it, acting as a scale down. If the empty time to live is not provided, deployments created by the fleet will never be deleted, and you will need to delete them manually, which defeats the purpose of scaling.
Note that the autodeploy option in the application version's session config will ignore the maximum deployments option of the fleet's policies. The system will continue creating deployments and may result in unwanted behavior or deployments.
For that reason, we strongly advise to not use autodeploy with the fleets.
The autodeploy option is a simpler version of a fleet, where the system automatically creates deployments based on the demand of your application, without any minimum or maximum restrictions. It can be useful for applications that have a highly variable demand and need to scale up and down quickly without any constraints.
Once satisfied with your fleet, you will need to link an application version so it can automatically create deployments. You can link multiple versions to the same fleet.
Linked applications will be displayed on this page. You can also delete the link between your fleet and your application here.
Unlinking an application version will not delete your fleet or your application. It will simply tell your fleet to stop doing new deployments for this specific version.
The fleet will not delete current deployments; you need to delete them manually if your application version doesn't have an empty time to live in the session config.
