AWS eks documentation change
Summary
Removed XML-style replaceable tags from CLI commands and improved command formatting
Security assessment
Formatting changes for clarity; no security-related content added or modified
Diff
diff --git a/eks/latest/userguide/capabilities-troubleshooting.md b/eks/latest/userguide/capabilities-troubleshooting.md index 7681c3083..76e12c92c 100644 --- a//eks/latest/userguide/capabilities-troubleshooting.md +++ b//eks/latest/userguide/capabilities-troubleshooting.md @@ -108 +108 @@ EKS Capabilities create and manage Kubernetes Custom Resource Definitions (CRDs) - kubectl get <replaceable>resource-kind</replaceable> -A + kubectl get resource-kind -A @@ -111 +111,2 @@ EKS Capabilities create and manage Kubernetes Custom Resource Definitions (CRDs) - kubectl describe <replaceable>resource-kind</replaceable> <replaceable>resource-name</replaceable> -n <replaceable>namespace</replaceable> + kubectl describe resource-kind + resource-name -n namespace @@ -114 +115,2 @@ EKS Capabilities create and manage Kubernetes Custom Resource Definitions (CRDs) - kubectl get <replaceable>resource-kind</replaceable> <replaceable>resource-name</replaceable> -n <replaceable>namespace</replaceable> -o jsonpath='{.status.conditions}' + kubectl get resource-kind + resource-name -n namespace -o jsonpath='{.status.conditions}' @@ -117 +119,2 @@ EKS Capabilities create and manage Kubernetes Custom Resource Definitions (CRDs) - kubectl get events --field-selector involvedObject.name=<replaceable>resource-name</replaceable> -n <replaceable>namespace</replaceable> + kubectl get events --field-selector involvedObject.name=resource-name -n namespace + @@ -140 +143 @@ Verify the Capability Role has the necessary permissions: - aws iam list-attached-role-policies --role-name <replaceable>my-capability-role</replaceable> + aws iam list-attached-role-policies --role-name my-capability-role @@ -143 +146 @@ Verify the Capability Role has the necessary permissions: - aws iam list-role-policies --role-name <replaceable>my-capability-role</replaceable> + aws iam list-role-policies --role-name my-capability-role @@ -146 +149 @@ Verify the Capability Role has the necessary permissions: - aws iam get-role-policy --role-name <replaceable>my-capability-role</replaceable> --policy-name <replaceable>policy-name</replaceable> + aws iam get-role-policy --role-name my-capability-role --policy-name policy-name @@ -149 +152 @@ Verify the Capability Role has the necessary permissions: - aws iam get-role --role-name <replaceable>my-capability-role</replaceable> --query 'Role.AssumeRolePolicyDocument' + aws iam get-role --role-name my-capability-role --query 'Role.AssumeRolePolicyDocument' @@ -175,2 +178,3 @@ All capabilities require proper EKS Access Entries and Access Policies on the cl - --cluster-name <replaceable>my-cluster</replaceable> \ - --region <replaceable>region-code</replaceable> + --cluster-name my-cluster \ + --region region-code + @@ -184,3 +188,4 @@ Look for the Capability Role ARN in the list. If missing, the capability cannot - --cluster-name <replaceable>my-cluster</replaceable> \ - --principal-arn <replaceable>arn:aws:iam::111122223333:role/my-capability-role</replaceable> \ - --region <replaceable>region-code</replaceable> + --cluster-name my-cluster \ + --principal-arn arn:aws:iam::111122223333:role/my-capability-role \ + --region region-code + @@ -206,3 +211,4 @@ If deploying to remote clusters, verify the Capability Role has an Access Entry - --cluster-name <replaceable>target-cluster</replaceable> \ - --principal-arn <replaceable>arn:aws:iam::111122223333:role/argocd-capability-role</replaceable> \ - --region <replaceable>region-code</replaceable> + --cluster-name target-cluster \ + --principal-arn arn:aws:iam::111122223333:role/argocd-capability-role \ + --region region-code +