< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />

View Composed App Details

This section describes how to view composed app details.

Prerequisites

You should join a project and have the Service Mesh View permission within the project. For more information, refer to "Project Members" and "Project Roles".

Steps

  1. Log in to the KubeSphere web console with a user who has the Service Mesh View permission, and access your project.

  2. Click Service Mesh > Composed Apps in the left navigation pane.

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

  4. On the app details page, view the app’s resource attributes in the Attributes area on the left.

    ParameterDescription

    Cluster

    The cluster to which the app belongs.

    Project

    The project to which the app 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 creation time of the application.

    Update Time

    The update time of the application.

    Creator

    The user who created the application.

    Application Governance

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

  5. On the app details page, view the Ingresses, services, and workloads that make up the app in the Resource Status tab.

    • The Ingresses area provides the following information:

      ParameterDescription

      Name

      The name of the Ingress.

      Domain

      The domain 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 Services area provides the following information:

      ParameterDescription

      Name

      The name of the service.

      Internal Access Mode

      The internal access mode for the service.

      • Headless: The system does not assign a virtual IP address to the service. It can be accessed internally by using the 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 access within the cluster. It also supports access internally by using the format <service name>.<project name>.svc.cluster.local or <service name>.<project name>.

      Virtual IP Address

      The virtual IP address for internal access within the cluster. Only displayed when the service’s internal access type is VirtualIP.

    • The Workloads area provides the following information:

      ParameterDescription

      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 expected and current pod replica count of the workload is 0.

      Revision Record

      The current revision record of the workload.

  6. On the app details page, click Traffic Monitoring on the right to view the app’s traffic information.

    Click a service in the graphic panel, and on the right side of the page, view the service’s traffic monitoring information, related pods, and perform Traffic Management.

    ParameterDescription

    Traffic Policies > Load Balancing

    Load Balancing Algorithm

    • Round Robin: Distributes client requests to backends in rotation.

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

    • Random: Sends client requests to a backend randomly selected from all healthy backends.

    • Pass Through: Directly forwards the connection to the original IP address of the caller’s request without any form of load balancing. It is for advanced configurations, please use with caution.

    Traffic Policies > Session Persistence

    Maps requests to backend servers based on specific identifiers (e.g., HTTP header, Cookie, query parameter) to achieve balanced distribution and load sharing.

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

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

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

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

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

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

    For more information, see this document.

    Connection Pool

    Creates a fixed number of connection objects for the application and stores them in a connection pool for reuse. A connection object is retrieved from the connection pool for each request and returned to the pool after use.

    After enabling, 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 cannot be accessed and the specified criteria are met, the ciruit breaker marks the service as unavailable and returns error response to clients directly for a specified period of time.

    After enabling, set the number of consecutive 5XX errors, inspection interval (seconds), maximum ejection ratio (%), and base ejection time (seconds).

  7. On the app details page, click Grayscale Release on the right to view the app’s grayscale release information. For more information, see Grayscale Release.

    Note

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

  8. On the app details page, click Tracing on the right to view the app’s request tracing information.

    Note
    • To use the Tracing feature, you need to enable application governance when creating a composed app. For more information, see Create Composed Apps.

    • Additionally, you need to enable the project gateway and enable the Tracing feature for the project gateway. For more information, see Enable Project Gateway.

Receive the latest news, articles and updates from KubeSphere


Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

What’s on this Page