This section describes how to view composed app details.

Prerequisites

You need to join a project and have the Service Mesh View permission in the project. For more information, see Project Members and Project Roles.

Steps

  1. Log in to the KubeSphere web console with a user who has Service Mesh View permissions and enter your workspace.

  2. Click Grayscale Release > Composed Apps in the left navigation pane.

  3. Select a project from the drop-down list in the upper left corner of the page.

  4. On the Composed Apps page, click the name of an app to open its details page.

  5. On the app details page, view the resource attributes of the app in the Attributes area.

    Parameter Description

    Cluster

    The cluster to which the application belongs.

    Project

    The project to which the application belongs.

    Status

    The current status of the application.

    • Creating: The system is creating the application.

    • Running: The application is running normally.

    • Upgrading: The system is upgrading the application version.

    • Deleting: The system is deleting the application.

    • Failed: The application creation failed.

    Version

    The version of the application.

    Creation Time

    The time when the application was created.

    Update Time

    The time when the application was updated.

    Creator

    The user who created the application.

    App Governance

    Whether app governance is enabled for the app. After app governance is enabled, you can use traffic monitoring, grayscale release, and tracing features.

  6. On the Resource Status tab of the application details page, view the Ingresses, Services, and workloads that make up the application. Click the resource name to jump to the corresponding resource details page.

    • The Ingress area provides the following information:

      Parameter Description

      Name

      The name of the Ingress.

      Domain

      The domain name of the Ingress.

      URL

      The access address of the service corresponding to the Ingress.

      Click Access Service on the right side of the Ingress to access the backend service of the Ingress.

    • The Service area provides the following information:

      Parameter Description

      Name

      The name of the Service.

      Internal Access Mode

      Internal Access Mode for Services.

      • Headless: The system does not assign a virtual IP address to the service. It can be accessed from within the cluster using the domain name format <service name>.<project name>.svc.cluster.local or <service name>.<project name>.

      • VirtualIP: The system assigns a virtual IP address to the service for internal cluster access. It also supports access from within the cluster using the domain name format <service name>.<project name>.svc.cluster.local or <service name>.<project name>.

      Virtual IP Address

      The virtual IP address used for internal cluster access to the Service. Displayed only when the Service’s internal access type is VirtualIP.

    • The Workload area provides the following information:

      Parameter Description

      Name

      The name of the workload.

      Type

      The type of the workload.

      Status

      The current status of the workload.

      • Running: The workload is running normally.

      • Updating: The workload is updating pod replicas.

      • Stopped: Both the desired and current pod replica counts for the workload are 0.

      Modification Record

      The current modification record of the workload.

  7. On the app details page, click Traffic Monitoring to view the traffic information of the app.

    Click a service in the graph panel, and on the right side of the page, view the traffic monitoring information and related pod information of the service, and perform Traffic Management.

    Parameter Description

    Traffic Policy > Load Balancing

    Load balancing algorithm

    • Round Robin: Sends client requests to backends in turn.

    • Least Request: Randomly selects two healthy backends and sends client requests to the backend with fewer requests.

    • Random: Sends client requests to a random healthy backend.

    • Pass Through: Forwards connections directly to the original IP address requested by the caller without any form of load balancing. Used for advanced configuration. Use with caution.

    Traffic Policy > Session Persistence

    Maps requests to backend servers based on specific identifiers (such as HTTP headers, cookies, query parameters, etc.) to achieve balanced distribution and load sharing of requests.

    • Hash based on HTTP Header: Hash based on a specific HTTP header.

    • Hash based on HTTP Cookie: Hash based on an HTTP cookie.

    • Hash based on HTTP Query Parameter: Hash based on a specific HTTP query parameter.

    • Hash based on Source IP Address: Hash based on the source IP address. Applicable to TCP and HTTP connections.

    • Hash based on ring/modulo: The ring/modulo hash load balancer uses a consistent hashing algorithm to hash backend hosts.

    • Hash based on Maglev: The Maglev hash load balancer uses a consistent hashing algorithm to hash backend hosts.

    For more information, refer to this document.

    Connection Pool

    Creates a fixed number of connection objects for the application and stores them in a connection pool for reuse. Each request obtains a connection object from the pool and returns it to the pool after use.

    After enabling, you need to set the maximum number of connections, maximum requests per connection, maximum retries, connection timeout, maximum request quantity, and maximum pending request quantity.

    Circuit Breaker

    If a service is inaccessible and meets specified conditions, the circuit breaker marks the service as unavailable and directly returns an error response to the client within a specified time range.

    After enabling, you need to set the consecutive 5XX error count, check interval (seconds), maximum ejection percentage (%), and ejection time (seconds).

  8. On the app details page, click Grayscale Release to view the grayscale release information of the app. For more information, refer to Grayscale Release.

    Note

    To use the Traffic Monitoring and Grayscale Release features, you need to enable the app governance feature when creating the composed app. For more information, refer to Create a Composed App.

  9. On the app details page, click Tracing to view the request tracing information of the app.

    Note

    • To use the Tracing feature, you need to enable the app governance feature when creating the composed app. For more information, refer to Create a Composed App.

    • You also need to enable the project gateway and enable the Tracing feature for the project gateway. For more information, refer to Enable a Project Gateway.