AWS eks documentation change
Summary
Updated examples and terminology: changed cluster name reference in Application resource example from 'my-cluster' to 'in-cluster', added clarification note about using cluster names for destination, replaced 'Git repositories' with 'sources' and 'declarative sources'.
Security assessment
Changes involve clarifications and terminology updates without addressing security vulnerabilities or introducing security features. No security context is present in the modifications.
Diff
diff --git a/eks/latest/userguide/argocd.md b/eks/latest/userguide/argocd.md index 3c27bb1cf..d103787b4 100644 --- a//eks/latest/userguide/argocd.md +++ b//eks/latest/userguide/argocd.md @@ -53 +53 @@ The following example shows how to create an Argo CD `Application` resource: - name: my-cluster + name: in-cluster @@ -59,0 +60,4 @@ The following example shows how to create an Argo CD `Application` resource: +###### Note + +Use `destination.name` with the cluster name you used when registering the cluster (like `in-cluster` for the local cluster). The `destination.server` field also works with EKS cluster ARNs, but using cluster names is recommended for better readability. + @@ -87 +91 @@ To get started with the EKS Capability for Argo CD: - 1. Create and configure an IAM Capability Role with the necessary permissions for Argo CD to access your Git repositories and manage applications. + 1. Create and configure an IAM Capability Role with the necessary permissions for Argo CD to access your sources and manage applications. @@ -93 +97 @@ To get started with the EKS Capability for Argo CD: - 4. Create Application resources to deploy your applications from Git repositories. + 4. Create Application resources to deploy your applications from your declarative sources.