ACK One GitOps lets you build Continuous Delivery (CD) pipelines for applications across multi-cloud, multi-cluster, and hybrid cloud environments. It integrates fully managed Argo CD with the multi-cluster management feature of ACK One, Resource Access Management (RAM), and Alibaba Cloud single sign-on (SSO). With these integrations, ACK One GitOps provides out-of-the-box Argo CD capabilities and a secure, end-to-end GitOps experience for multi-cluster application delivery.
How it works
ACK One GitOps uses ACK One GitOps and Container Registry to build a CD pipeline that spans multiple deployment phases: Development, Staging, and Production.
When you push code changes to a Git repository, the CD pipeline detects the change and triggers application updates with the latest container images. The updated applications are then deployed to clusters in the corresponding environment.
The sync behavior differs by phase:
| Phase | Sync policy | Notes |
|---|---|---|
| Development | Automatic | Applications sync immediately when new images are available. |
| Staging | Manual | Changes require explicit approval before rollout. Use canary releases to validate before full deployment. |
| Production | Manual | Changes require explicit approval before rollout. Use canary releases to reduce risk. |
Benefits
No Argo CD infrastructure to operate
ACK One GitOps is O&M-free and provides out-of-the-box features. There is no Argo CD infrastructure to install, configure, or maintain on your own clusters.
Familiar Argo CD CLI and UI
ACK One GitOps exposes the same CLI and UI as upstream Argo CD. Existing Argo CD workflows and tooling work without modification.
Centralized access control for multi-tenant teams
A dedicated Argo CD console integrates with RAM and Alibaba Cloud SSO. Manage permissions at the team or project level to support multi-tenancy scenarios.
Automatic cluster registration
When you associate a cluster with ACK One, Argo CD is automatically enabled for that cluster. Secrets and service accounts manage the permissions to access clusters that are associated with ACK One.
Single template, multiple clusters with ApplicationSet
Use Argo CD ApplicationSet to define a single template and distribute the same application across multiple clusters. This eliminates the need to maintain separate Argo CD Application manifests for each cluster.
Use cases
ACK One GitOps targets DevOps and platform engineering teams that need to:
-
Deploy the same application to clusters across multiple regions or environments from a single control point
-
Enforce different sync policies per environment (automatic for development, gated for production)
-
Centralize access control for GitOps pipelines in organizations with multiple teams