#Overview

provides a unified interface to create, edit, delete, and manage cloud-native applications through both a web console and CLI (Command-Line Interface). Applications can be deployed across multiple namespaces with RBAC policies.

#Namespace Management

Namespaces provide logical isolation for Kubernetes resources. Key operations include:

• Creating Namespaces: Define resource quotas and pod security admission policies.
• Importing Namespaces: Importing existing Kubernetes namespaces into provides full platform capabilities parity with natively created namespaces.

#Application-management workflows

Use the consolidated pages under Building Applications for ongoing application lifecycle work.

Most migrated web console workflows still follow the same scope model:

• Application dashboards and summary views can aggregate data across the clusters associated with the current project.
• Concrete create, update, inspect, or troubleshooting actions still run in a selected cluster and namespace context.
• The same resource type can appear in both the Applications view and the Clusters view, but the entry path changes the task framing and operational scope.

Depending on the current project, enabled integrations, and your permissions, the console can show different tabs, actions, warning banners, or monitoring signals for the same task family.

#Application Lifecycle Management

supports end-to-end lifecycle management including:

#Application Creation Patterns

In , applications can be created in multiple ways. Here are some common methods:

• Create from Images: Create custom applications using pre-built container images. This method supports creating complete application that include Deployments, Services, ConfigMaps, and other Kubernetes resources.
• Create from Catalog: provides application catalogs, allowing users to select predefined application templates (Helm Charts or Operator Backed) for creation.
• Create from YAML: By importing a YAML file, create a custom application with all included resources in one step.
• Create from Code: Build images via Source to Image (S2I).

These pages are also the main landing points for migrated application-creation workflows from the newer console experience.

#Application Operations

• Updating Applications: Update an application's image version, environment variables, and other configurations, or import existing Kubernetes resources for centralized management.
• Exporting Applications: Export applications in YAML, Kustomize, or Helm Chart formats, then import them to create new application instances in other namespaces or clusters.
• Version Management: Support automatically or manually creating application versions, and in case of issues, one-click rollback to a specific version is available for quick recovery.
• Deleting Applications: Delete an application, it simultaneously deletes the application itself and all of its directly contained Kubernetes resources. Additionally, this action severs any association the application might have had with other Kubernetes resources that were not directly part of its definition.

#Application Observability

For continuous operation management, the platform provides logs, events, monitoring, etc.

• Logs: Supports viewing real-time logs from the currently running Pod, and also provides logs from previous container restarts.
• Events: Supports viewing event information for all resources within a namespace.
• Monitoring Dashboards: Provides monitoring dashboards for Applications, Workloads, and Pods. The Applications Overview dashboard is project-scoped, while workload and Pod dashboards remain namespace-scoped. You can also customize dashboards to suit specific operational requirements.

#Kubernetes Workload Management

Support for core workload types:

• Deployments: Manage stateless applications with rolling updates.
• StatefulSets: Run stateful apps with stable network IDs.
• DaemonSets: Deploy node-level services (e.g., log collectors).
• CronJobs: Schedule batch jobs with retry policies.

The workload pages under building_application are also the primary landing points for migrated workload workflows from the newer console experience.