SaaS Runtime Operations

Overview

In K2cloud SaaS, K2view operates the underlying platform and Kubernetes infrastructure while customers continue to operate their K2view implementations.

Customer runtime activities commonly include:

• managing Studio and Fabric Spaces,
• promoting deployments,
• activating environments,
• validating runtime behavior,
• reviewing monitoring and logs,
• troubleshooting application and deployment issues,
• and managing runtime access.

These operations remain centered around Spaces and are performed through K2cloud and the applications within each Space.

Space Lifecycle Operations

Authorized customers manage the application-level lifecycle of their Spaces through K2cloud Orchestrator.

Depending on the Space type, operations can include:

• reviewing Space status,
• opening Spaces,
• refreshing status,
• pausing and resuming Studio Spaces,
• restarting Fabric Spaces,
• reviewing Space Details,
• and deleting Spaces.

K2view operates the infrastructure on which these lifecycle operations execute.

For detailed Space operations, see K2cloud Spaces.

Deployment Operations

Customers control promotion of their K2view implementation into runtime Spaces.

The standard deployment sequence is:

Approved Git Tag
      ↓
Deploy Environment
      ↓
Activate Environment
      ↓
Deploy Project
      ↓
Validate Runtime

The customer determines what version should be deployed, where it should be deployed, and whether the resulting application operates correctly.

For detailed deployment procedures, see K2cloud Deployments and Lifecycle.

Runtime Access

Runtime users access authorized Spaces directly through the Space URL.

Depending on the Space and the user's permissions, this can provide access to capabilities such as:

• Fabric Web Studio,
• Fabric Admin,
• TDM,
• APIs,
• Reports,
• and other runtime applications.

Customers remain responsible for defining the appropriate runtime authorization and managing the identity groups used to provide that access.

K2cloud Orchestrator access is separate from Space runtime access.

For more information, see K2cloud Identity and Access.

Runtime Monitoring

K2cloud SaaS provides integrated monitoring and logging capabilities for customer Spaces.

Customers can use these capabilities to review:

• Space activity,
• runtime metrics,
• logs,
• deployment activity,
• and runtime behavior.

These capabilities provide application and operational visibility without requiring customers to operate the underlying monitoring infrastructure.

For more information, see Monitoring and Logs.

Runtime Diagnostics

When troubleshooting a Space, customers can also use Space Details to inspect Kubernetes-level diagnostics exposed through K2cloud.

These include:

• pod state,
• pod details,
• pod logs,
• resource information,
• and Kubernetes events.

A typical investigation can therefore move from application-level visibility to Kubernetes-level diagnostics:

Review Space status
        ↓
Review Metrics and Logs
        ↓
Review Space Details
        ↓
Review pod state and logs
        ↓
Review Kubernetes events

Customers can inspect this information without directly administering the underlying Kubernetes infrastructure.

For more information, see View Space Details.

Troubleshooting Responsibility

Customers remain responsible for troubleshooting issues related to their K2view implementation, including:

• deployment content,
• environment configuration,
• application behavior,
• integrations,
• runtime authorization,
• and application logic.

K2view remains responsible for the underlying K2cloud SaaS platform and infrastructure.

When investigation indicates that an issue concerns the SaaS platform or infrastructure rather than the customer implementation, the issue should be escalated to K2view.

See SaaS Observability and Support.

Related Documentation

• K2cloud SaaS Overview
• SaaS Operational Model
• K2cloud Spaces
• K2cloud Deployments and Lifecycle
• Monitoring and Logs
• SaaS Observability and Support