Amazon Web Services → Microsoft Azure
Azure equivalent of Amazon EKS Capabilities (Argo CD, ACK, kro)
Amazon EKS Capabilities (managed Argo CD, ACK, and kro) map partly to AKS GitOps extensions (Flux v2 and Argo CD).
About Amazon EKS Capabilities (Argo CD, ACK, kro)
| Provider | Amazon Web Services |
|---|---|
| Status | Generally available |
| What it is | AWS-managed platform features that run in EKS rather than on your nodes. Argo CD for GitOps, AWS Controllers for Kubernetes (ACK) to manage AWS resources, and kro for composing resources. |
| Documentation | docs.aws.amazon.com |
| Pricing | Official pricing page |
Azure mappings (1)
| Capability | Azure equivalent | Match |
|---|---|---|
| Managed GitOps and platform add-ons for Kubernetes | GitOps for AKS (Flux v2 and Argo CD extensions) | Partial match |
Kubernetes(1)
Managed GitOps and platform add-ons for Kubernetes Partial match
Amazon EKS Capabilities (managed Argo CD, ACK, and kro) map partly to AKS GitOps extensions (Flux v2 and Argo CD). AWS runs these components outside your cluster, while Azure installs them as managed cluster extensions.
- Where it runs. EKS Capabilities run in EKS-owned infrastructure, not on your worker nodes. Azure GitOps extensions run in your cluster and are lifecycle-managed by Azure.
- Cloud resources from Kubernetes. ACK manages AWS resources with Kubernetes CRDs. The Azure counterpart is Azure Service Operator (open source, self-installed), which isn't a managed extension.
- Fleet. Azure Kubernetes Fleet Manager adds multi-cluster update orchestration and resource propagation (some features in preview). AWS has no first-party fleet manager for EKS beyond Argo CD multi-cluster.