Skip to main content

Start & Stop Environment

Atmosly allows you to start and stop entire environments, scaling all services up or down at once.

Steps​

  1. Navigate to the Environments list.
  2. Click the three-dot menu next to the environment.
  3. Select Start or Stop and confirm your selection.

Stopping an Environment​

When you stop an environment, all service pods are scaled down to zero. The application becomes inaccessible from its endpoints.

Stop environment

Status transitions when stopping:

  1. Environment phase changes to Decommissioning Resources.
  2. Each service status changes to Stopping, then Stopped.
  3. Once all services are stopped, the environment phase becomes Unavailable.
note

You cannot stop an environment that is already in the Unavailable state.

Starting an Environment​

When you start an environment, all pods that were scaled to zero are restored, and the application becomes accessible from its endpoints.

Start environment

Status transitions when starting:

  1. Environment phase changes to Provisioning Resources.
  2. Each service status changes to Starting, then Healthy or Running.
  3. Once all services are running, the environment phase becomes Active.
note

You can only start an environment that is in the Unavailable state.

Partial States​

If some services fail to start or stop while others succeed, the environment enters a partial state:

StateDescription
Partially ActiveSome services are running while others remain stopped after a start operation.
Partially StoppedSome services have been stopped while others remain running after a stop operation.
tip

If your environment is stuck in a partial state, use the Reconcile action from the three-dot menu to sync the displayed state with the actual Kubernetes cluster state. You can then retry the start or stop operation.