Removing deployments

Feature set: Inference Contact our support for access.
This functionality evolves quickly, the behavior and APIs might change between releases without further notice.

Tearing down what a descriptor created releases the hardware it held. Deletion runs in the reverse of apply order, so no hostname is left pointing at a model that has already gone.

Saving what is running first

Export writes everything running back out as a descriptor, routes included:

akka models export > snapshot.yaml

This is the way to capture a deployment that was built with direct commands rather than from a file. The result is ready to version control, with one exception: strip any token out of it first, for the reason given in Supplying a token for gated weights.

Export masks secret values with NOT EXPORTED. Applying an exported file unedited fails validation rather than overwriting a live secret with the mask. Replace the value, or delete the secret document and create the secret ahead of time.

Removing what a descriptor names

akka models delete -f models.yaml

Routes are removed first, then deployments, then the resources they depended on.

Cached weights survive by default, so the next apply does not download them again. To remove the cache as well:

akka models delete -f models.yaml --include-cache

Removing a single deployment

akka models delete docs

This deletes one deployment by name, without a descriptor. The accelerator it ran on stays, and its capacity becomes available to another model. See Releasing capacity to remove the accelerator too.

API keys survive teardown. Deleting a route does not revoke the keys issued against it, and rebuilding the route under the same name makes every key ever issued to it work again. Remove keys explicitly with akka models routes keys remove, described in Issuing API keys.

 

The features described in this section are an add-on to Akka Automated Operations. They are not included in the base product.

See also