What's New

Restart and Recreate a container instance Occasionally, a workload may run for awhile on your node and then some part of the application might hang. In these cases, it's typically faster to get back up and running by restarting the container on the same node, rather than searching for a new one. The Restart option allows you to restart your container on the node, with all settings and downloaded data intact. For a harder reset, the Recreate option allows you to rebuild the container from scratch on the node. These features are accessible from the actions dropdown next to each node on the container group detail page:

Startup and Liveness Health Probes Health probes provide an automated way for you to trigger certain actions based on the status of the containers in a container group deployment. Startup Probes run on container startup, and are typically used to check that your application has started. Liveness Probes run after your startup probe has completed successfully, and are typically used to check that your application is running correctly. For more details on setting up these probes, see our documentation here. These optional features can be enabled and configured from the container group configuration screen.

Improved node selection and workload allocation We've upgraded the backend node selection logic to more quickly and reliably allocate nodes to your workloads, improving overall utilization of the network and increasing the number of nodes available to you at any time.

Bug Fixes

You should expect more reliable, faster node deployments as we've fixed several intermittent errors with downloading and starting workloads.
We've fixed multiple UI bugs that, in certain edge cases, could impact the user experience on the Salad Cloud Portal.