Container Service for Kubernetes:Create a multi-cluster application

Procedure

1. Log on to the ACK One console. In the left-side navigation pane, choose Fleet > Multi-cluster GitOps.

2. In the upper-left corner of the Multi-cluster GitOps page, click the icon next to the fleet name, and then select the target fleet from the drop-down list.

3. Click Create Multi-cluster Application > GitOps to open the Create Multi-cluster Application - GitOps page.

4. On the Quick Create tab, configure the parameters as described below.

   Configuration item		Description	Example
   Multi-cluster Application Set Name		The name of the application.	appset-echo-server-demo
   Project		The project to which the application belongs.	default
   Source Code URL		The source code address of the application.	https://github.com/AliyunContainerService/gitops-demo.git
   Git Branch		The Git branch of the application.	main
   Path		The relative path of the YAML file defined by the application in the Git repository.	manifests/helm/echo-server
   Destination Cluster		The destination cluster to which the application is deployed. If you do not specify a destination cluster, all clusters in ArgoCD except for the in-cluster (the fleet and the cluster where ArgoCD resides) are automatically configured as destination clusters.
   Namespace		The namespace in the cluster where the application is deployed.	demo
   Application Name		The application name. The following parameters are available by default: {{.name}} {{.metadata.annotations.cluster_name}} {{.metadata.annotations.cluster_id}}	{{.metadata.annotations.cluster_id}}-echoserver
   Advanced Configuration	Synchronization Policy (application Set)	PRESERVE RESOURCES ON DELETION: If you select this check box, the child resources of the application are retained when this application set is deleted.
   	Synchronization Policy (application)	Manual: manual sync. Automatic: automatic sync. PRUNE RESOURCES: If you select this check box, resources that do not have a corresponding configuration in the Git repository are automatically deleted from the cluster. SELF HEAL: If you select this check box, the actual state of resources is automatically synchronized with the desired state in the Git repository. This prevents the status of cluster resources from being inconsistent with the status in the Git repository due to manual modifications.

   The following table describes the parameters that you need to synchronize.

   Parameter	Description
   SKIP SCHEMA VALIDATION	Specifies whether to validate the resource specification format. This is equivalent to "kubectl apply --validate=true|false". The default value is true.
   AUTO-CREATE NAMESPACE	Automatically creates missing namespaces.
   PRUNE LAST	Prunes resources at the end of a sync operation, after all other resources are deployed and healthy.
   APPLY OUT OF SYNC ONLY	Synchronizes only the resources that are in the OutOfSync state. This speeds up the synchronization process.
   RESPECT IGNORE DIFFERENCES	Ignores the desired state fields during the synchronization phase.
   SERVER-SIDE APPLY	Enables Kubernetes Server-Side Apply. You can use server-side apply if a resource is too large to fit within the allowed annotation size, you need to patch existing resources on a cluster that are not fully managed by Argo CD, or if you want to use a more declarative approach to track the field management of users.
   REPLACE	Modifies resources using the replace method instead of the default apply method. The replace method first deletes and then creates a resource. The apply method updates a resource using a patch.
   RETRY	Allows you to specify the number of retries, retry interval, and retry interval increment policy after a sync fails.

   For more information about sync options, see Argo CD Sync Options.

5. If the Quick Create tab does not meet your requirements, select the Create from YAML tab and configure the parameters based on the provided example.

   Note

   Quick Create is synchronized with Create from YAML, and any changes are reflected in the YAML content within Create from YAML.

6. After you complete the configuration, click OK. The application status is displayed in the Status column on the Multi-cluster GitOps page.

7. Click the number in the Application column that corresponds to the target application Name to view a summary of the application created by the multi-cluster application. Click the Application Name to go to the ArgoCD UI.