A Space moves through lifecycle states as it is created, operated, deployed, paused, resumed, restarted, and deleted.
The K2cloud Orchestrator coordinates these lifecycle activities and displays the current operational state of the Space.
Common Space states include:
The visible state reflects the current operational condition of the Space.
The Space card displays Status Change, which identifies the most recent state transition for the Space.
A status change can result from operations such as:
Status Change is not an activity or audit history. It represents the latest change in the operational state of the Space.
Studio Spaces support lifecycle operations such as:
Pausing a Studio Space suspends runtime execution while preserving the Space definition.
When required, the Space can subsequently be resumed.
Fabric Spaces are runtime-oriented and do not support Pause and Resume.
Their lifecycle operations include:
For details about these operations, see Operate a Space.
Project Managers with the cloud_user role perform Space lifecycle operations through the K2cloud Orchestrator.
Runtime users can access a Space directly when authorized through roles such as space_admin, space_user, or customer-defined Fabric roles.
Space authorization alone does not provide access to K2cloud Orchestrator lifecycle operations. A user must also have the cloud_user role to perform those operations through the Orchestrator.
Deletion is the final lifecycle operation and is not recoverable.
The effect on persistent data depends on the persistence model used by the Space Profile.
Before deleting a Space, see Delete a Space.
A Space moves through lifecycle states as it is created, operated, deployed, paused, resumed, restarted, and deleted.
The K2cloud Orchestrator coordinates these lifecycle activities and displays the current operational state of the Space.
Common Space states include:
The visible state reflects the current operational condition of the Space.
The Space card displays Status Change, which identifies the most recent state transition for the Space.
A status change can result from operations such as:
Status Change is not an activity or audit history. It represents the latest change in the operational state of the Space.
Studio Spaces support lifecycle operations such as:
Pausing a Studio Space suspends runtime execution while preserving the Space definition.
When required, the Space can subsequently be resumed.
Fabric Spaces are runtime-oriented and do not support Pause and Resume.
Their lifecycle operations include:
For details about these operations, see Operate a Space.
Project Managers with the cloud_user role perform Space lifecycle operations through the K2cloud Orchestrator.
Runtime users can access a Space directly when authorized through roles such as space_admin, space_user, or customer-defined Fabric roles.
Space authorization alone does not provide access to K2cloud Orchestrator lifecycle operations. A user must also have the cloud_user role to perform those operations through the Orchestrator.
Deletion is the final lifecycle operation and is not recoverable.
The effect on persistent data depends on the persistence model used by the Space Profile.
Before deleting a Space, see Delete a Space.