Common Operations Overview
Overview
Operating a K2cloud environment involves several areas covered throughout the K2cloud documentation, including:
- Projects,
- Sites,
- Space Profiles,
- Spaces,
- deployments,
- identity and access,
- and monitoring and diagnostics.
This section does not redefine those capabilities or repeat their procedures.
Instead, it brings them together from an operational perspective to help teams prepare for and consistently operate K2cloud environments across development, QA, staging, and production.
Operational Ownership
K2cloud environments typically involve several operational responsibilities.
The exact division of responsibility depends on whether the environment uses K2cloud SaaS or K2cloud Self-Hosted.
For the detailed responsibility model, see Shared Responsibility Model.
Common Operational Activities
Common K2cloud operational activities include:
- creating and deleting Spaces,
- pausing and resuming Studio Spaces,
- restarting Fabric Spaces,
- reviewing Space status,
- reviewing Kubernetes pod diagnostics and events,
- deploying and activating environment definitions,
- deploying Project content,
- validating deployments,
- monitoring runtime activity and logs where available,
- and managing identity and access.
The detailed procedures belong to their respective areas of the K2cloud documentation.
Space Operations
Space lifecycle, diagnostics, monitoring, and other Space operations are covered in K2cloud Spaces.
Deployments
Environment and Project deployment workflows are covered in K2cloud Deployments and Lifecycle.
Identity and Access
Authentication, federation, roles, permissions, and Space access are covered in K2cloud Identity and Access.
Operational Readiness
Before moving an implementation into production, operational responsibilities and procedures should be understood and validated.
This includes confirming:
- infrastructure readiness,
- Space configuration,
- persistence and storage,
- connectivity,
- deployment procedures,
- identity and access,
- monitoring and diagnostics,
- and operational ownership.
Use the Production Readiness Checklist as a final operational review.
Operational Runbooks
Organizations should establish operational runbooks for recurring or exceptional activities that require a defined response.
Rather than duplicating the procedures documented throughout K2cloud, the runbook framework identifies the operational procedures teams should have available and points to the corresponding K2cloud documentation.
See Operational Runbooks.
Related Documentation
Common Operations Overview
Overview
Operating a K2cloud environment involves several areas covered throughout the K2cloud documentation, including:
- Projects,
- Sites,
- Space Profiles,
- Spaces,
- deployments,
- identity and access,
- and monitoring and diagnostics.
This section does not redefine those capabilities or repeat their procedures.
Instead, it brings them together from an operational perspective to help teams prepare for and consistently operate K2cloud environments across development, QA, staging, and production.
Operational Ownership
K2cloud environments typically involve several operational responsibilities.
The exact division of responsibility depends on whether the environment uses K2cloud SaaS or K2cloud Self-Hosted.
For the detailed responsibility model, see Shared Responsibility Model.
Common Operational Activities
Common K2cloud operational activities include:
- creating and deleting Spaces,
- pausing and resuming Studio Spaces,
- restarting Fabric Spaces,
- reviewing Space status,
- reviewing Kubernetes pod diagnostics and events,
- deploying and activating environment definitions,
- deploying Project content,
- validating deployments,
- monitoring runtime activity and logs where available,
- and managing identity and access.
The detailed procedures belong to their respective areas of the K2cloud documentation.
Space Operations
Space lifecycle, diagnostics, monitoring, and other Space operations are covered in K2cloud Spaces.
Deployments
Environment and Project deployment workflows are covered in K2cloud Deployments and Lifecycle.
Identity and Access
Authentication, federation, roles, permissions, and Space access are covered in K2cloud Identity and Access.
Operational Readiness
Before moving an implementation into production, operational responsibilities and procedures should be understood and validated.
This includes confirming:
- infrastructure readiness,
- Space configuration,
- persistence and storage,
- connectivity,
- deployment procedures,
- identity and access,
- monitoring and diagnostics,
- and operational ownership.
Use the Production Readiness Checklist as a final operational review.
Operational Runbooks
Organizations should establish operational runbooks for recurring or exceptional activities that require a defined response.
Rather than duplicating the procedures documented throughout K2cloud, the runbook framework identifies the operational procedures teams should have available and points to the corresponding K2cloud documentation.
See Operational Runbooks.
Related Documentation
