AWS eks documentation change
Summary
Fixed console URL formatting and added XML tags to replaceable parameters in kubectl commands
Security assessment
Changes involve URL formatting fixes and command template improvements. No security configurations or vulnerability mitigations introduced.
Diff
diff --git a/eks/latest/userguide/kro-troubleshooting.md b/eks/latest/userguide/kro-troubleshooting.md index 23d84d14e..9ee502704 100644 --- a//eks/latest/userguide/kro-troubleshooting.md +++ b//eks/latest/userguide/kro-troubleshooting.md @@ -29 +29 @@ You can view capability health and status issues in the EKS console or using the - 1. Open the Amazon EKS console at [https://console.aws.amazon.com/eks/home#/clusters](https://console.aws.amazon.com/eks/home#/clusters). + 1. Open the Amazon EKS console at https://console.aws.amazon.com/eks/home#/clusters. @@ -107,2 +107 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl describe custom-kind - my-instance + kubectl describe <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> @@ -111 +110 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get events --field-selector involvedObject.name=my-instance + kubectl get events --field-selector involvedObject.name=<replaceable>my-instance</replaceable> @@ -114,2 +113 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get custom-kind - my-instance -o jsonpath='{.status.conditions}' + kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status.conditions}' @@ -118,2 +116 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get custom-kind - my-instance -o jsonpath='{.status.state}' + kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status.state}' @@ -182 +179 @@ CEL expression errors are caught at ResourceGraphDefinition creation time, not w - kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.status.conditions[?(@.type=="ResourceGraphAccepted")]}' + kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.status.conditions[?(@.type=="ResourceGraphAccepted")]}' @@ -185,2 +182 @@ CEL expression errors are caught at ResourceGraphDefinition creation time, not w - kubectl describe resourcegraphdefinition my-rgd - + kubectl describe resourcegraphdefinition <replaceable>my-rgd</replaceable> @@ -219 +215 @@ kro automatically infers dependencies from CEL expressions and creates resources - kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.status.topologicalOrder}' + kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.status.topologicalOrder}' @@ -227,2 +223 @@ This shows the computed order based on CEL expression references between resourc - kubectl get custom-kind - my-instance -o jsonpath='{.status}' + kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status}' @@ -231 +226 @@ This shows the computed order based on CEL expression references between resourc - kubectl get deployment my-deployment -o jsonpath='{.status.conditions}' + kubectl get deployment <replaceable>my-deployment</replaceable> -o jsonpath='{.status.conditions}' @@ -247 +242 @@ The `readyWhen` field is optional. If not specified, resources are considered re - kubectl get events -n namespace --sort-by='.lastTimestamp' + kubectl get events -n <replaceable>namespace</replaceable> --sort-by='.lastTimestamp' @@ -260,2 +255 @@ If instances fail to create due to schema validation errors, verify the instance - kubectl describe custom-kind - my-instance | grep -A 5 "Validation" + kubectl describe <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> | grep -A 5 "Validation" @@ -280 +274 @@ If instances fail to create due to schema validation errors, verify the instance - kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.spec.schema}' + kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.spec.schema}'