GitOps high-availability mode

Usage notes

• In high-availability mode, GitOps uses six 2-vCPU, 4 GB ECI instances and one 4-vCPU, 8 GB ECI instance, and creates a few PrivateZone records. See Elastic Container Instance billing overview and PrivateZone product billing.

• High-availability mode supports up to 2,000 applications. If you exceed this limit and encounter performance issues, submit a ticket or join DingTalk group 35688562.

Prerequisites

• You have enabled the fleet management feature.

• GitOps is enabled in the ACK One fleet instance.

• The AliyunAdcpServerlessKubernetesRole role is granted to your account in the ACK One console.

  Important

  If you are logged in as a RAM user, your Alibaba Cloud account must also grant the RAM user the GetRole permission for RAM or attach the AliyunRAMReadOnlyAccess permission policy. Otherwise, the console will not function correctly.

• Alibaba Cloud CLI v3.0.172+ is installed and credentials are configured.

Enable GitOps high-availability mode

1. Enable GitOps high-availability mode for your ACK One fleet.

   1. If you have not enabled public access for GitOps:

      aliyun adcp UpdateHubClusterFeature --ClusterId <YOUR-FLEET-ID> --ArgoCDEnabled true --ArgoCDHAEnabled true

   2. If you have already enabled public access for GitOps:

      aliyun adcp UpdateHubClusterFeature --ClusterId <YOUR-FLEET-ID> --ArgoCDEnabled true --ArgoCDHAEnabled true --PublicAccessEnabled true 

2. Verify that high-availability mode is enabled.

   aliyun adcp DescribeHubClusterDetails --ClusterId <YOUR-FLEET-ID> | grep -B3 -A2 HA

   Expected output. HAEnabled is true, confirming the feature is enabled.

   "ACKOne": {
     "GitOps": {
       "Enabled": true,
       "HAEnabled": true
     }
   }

Disable GitOps high-availability mode

1. Disable GitOps high-availability mode for your ACK One fleet.

   aliyun adcp UpdateHubClusterFeature --ClusterId <YOUR-FLEET-ID> --ArgoCDEnabled true --ArgoCDHAEnabled false 

2. Log on to the PrivateZone console. On the Private Zone page, find the svc.cluster.local.<fleet-id> domain and delete all resolution records ending with .argocd.