AWS eks documentation change
Summary
Grammar improvements and updated ARN example formatting
Security assessment
Changes include grammatical corrections (e.g. 'aren't' to 'are not'), removal of redundant introductory text, and ARN placeholder replacement. No security-related content was modified or added.
Diff
diff --git a/eks/latest/userguide/argocd-troubleshooting.md b/eks/latest/userguide/argocd-troubleshooting.md index 4c288f490..5a84b6f09 100644 --- a//eks/latest/userguide/argocd-troubleshooting.md +++ b//eks/latest/userguide/argocd-troubleshooting.md @@ -7 +7 @@ -Capability is ACTIVE but applications aren’t syncingApplications stuck in "Progressing" stateRepository authentication failuresMulti-cluster deployment issuesNext steps +Capability is ACTIVE but applications are not syncingApplications stuck in "Progressing" stateRepository authentication failuresMulti-cluster deployment issuesNext steps @@ -15,2 +14,0 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -This topic provides troubleshooting guidance for the EKS Capability for Argo CD, including capability health checks, application sync issues, repository authentication, and multi-cluster deployments. - @@ -19 +17 @@ This topic provides troubleshooting guidance for the EKS Capability for Argo CD, -EKS Capabilities are fully managed and run outside your cluster. You don’t have access to Argo CD server logs or the `argocd` namespace. Troubleshooting focuses on capability health, application status, and configuration. +EKS Capabilities are fully managed and run outside your cluster. You do not have access to controller logs or controller namespaces. Troubleshooting focuses on capability health, application status, and configuration. @@ -21 +19 @@ EKS Capabilities are fully managed and run outside your cluster. You don’t hav -## Capability is ACTIVE but applications aren’t syncing +## Capability is ACTIVE but applications are not syncing @@ -23 +21 @@ EKS Capabilities are fully managed and run outside your cluster. You don’t hav -If your Argo CD capability shows `ACTIVE` status but applications aren’t syncing, check the capability health and application status. +If your Argo CD capability shows `ACTIVE` status but applications are not syncing, check the capability health and application status. @@ -167 +165 @@ Ensure the secret contains the correct authentication credentials (SSH key, toke -If applications aren’t deploying to remote clusters, verify the cluster registration and access configuration. +If applications are not deploying to remote clusters, verify the cluster registration and access configuration. @@ -191 +189 @@ On the target cluster, check that the Argo CD Capability Role has an Access Entr - --principal-arn arn:aws:iam::[.replaceable]111122223333:role/my-argocd-capability-role + --principal-arn arn:aws:iam::111122223333:role/my-argocd-capability-role