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

Create Composed Apps

This section describes how to create a composed app in a multi-cluster project.

You can customize the services, workloads, and routes of an app to create a composed app. Compared to template-based apps, composed apps support app governance. You can enable app governance for a composed app to use traffic monitoring, grayscale release, and link tracing features.

Prerequisites

  • Application Management for Cluster Federation should have been installed and enabled.

  • To enable app governance for the application, KubeSphere Service Mesh should have been installed and enabled.

  • You should join a multi-cluster project and have the Federated Project Management permission within the project.

Steps

  1. Log in to the KubeSphere web console with a user who has the Federated Project Management permission, and access your multi-cluster project.

  2. Click Application Workloads > Composed Apps in the left navigation pane.

  3. On the Apps page, click Create.

  4. On the Basic Information tab, set the basic information for the app, then click Next.

    ParameterDescription

    Name

    The name of the app. The name can only contain lowercase letters, numbers, and hyphens (-), must start and end with a lowercase letter or number, and can be up to 63 characters long.

    Version

    The user-defined version of the app. The version can only contain lowercase letters and numbers and can be up to 16 characters long.

    Application Governance

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

    Description

    The description of the app. The description can contain any characters and can be up to 256 characters long.

  5. On the Service Settings tab, click Create Service, select Stateful Service or Stateless Service to create a service for the app, then click Next.

    • Stateful Service: The internal access mode of the service is Headless, and the backend workload is Statefulset.

    • Stateless Service: The internal access mode of the service is VirtualIP, and the backend workload is Deployment.

    Note

    For more information, see Create a Stateful or Stateless Service.

  6. On the Ingress Settings tab, click Add Routing Rule to create routing rules for the app, then click Create.

    • In the Cluster area, select one or more clusters where the project belongs to add routing rules for the app in the specified clusters.

    • Click Add Routing Rule to set routing rules. You can set multiple routing rules, each corresponding to a domain name.

    • Hover the cursor over a created routing rule, then click pen on the right side to edit the routing rule settings.

    • Hover the cursor over a created routing rule, then click trash-light on the right side to delete the routing rule.

    ParameterDescription

    Domain

    The user-defined domain name.

    Protocol

    The protocol supported by the Ingress. The value can be HTTP or HTTPS.

    Secret

    The Secret used to provide the certificate and key when the Ingress protocol is HTTPS. This Secret must contain the tls.cert and tls.key fields, which store the Base64-encoded certificate and private key, respectively.

    Path

    The domain path and its mapping relationship with the service port.

    • Click Add to set multiple paths.

    • Click trash-light on the right side of a created path to delete the path.

    After the app is created, it will be displayed on the app list page.

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