Container Management
Outside of the configuration options that define how a container operates, there are settings that dictate how Cycle interacts with a container.
Reimaging a Container
Each container has a base image that can be updated as changes are made. This process is known as 'reimaging'. A reimage can be done on a running container, and all instances of the container will be updated.
Container Restart
Reimaging a container will restart it, and can lead to downtime.
New images are entirely downloaded to the node before the reimage happens to reduce the amount of time the instance will be offline.
Image Reconfigure
When reimaging, the user has the option to reconfigure (seen as "overwrite runtime config" in container reimage through portal). This action will replace the existing runtime configuration including the images environment variables.
Staggering Instance Reimages
Reimages can be staggered by utilizing the stagger field of the deployment container configuration.
Reimage a Container
Follow one of these interface-specific guides below.
Locking a Container
Containers can be set to "locked", meaning the platform will refuse to delete the container under all circumstances (via pipelines, bulk delete operations, and even will refuse to delete nodes with locked instances running on it).
Lock a Container
Follow one of these interface-specific guides below to lock a container.
Deprecating a Container
A container can be marked as deprecated to prevent it from being started. Deprecated containers also don't count against the resource usage of the cluster.
Follow one of these interface-specific guides below to deprecate a container.