AWS eks documentation change
Summary
Formatted kubectl commands for readability and replaced placeholders with example values in troubleshooting examples.
Security assessment
Changes improve command formatting and replace generic placeholders (e.g., <replaceable>my-rgd</replaceable>) with example values. No security-related content or vulnerabilities were addressed.
Diff
diff --git a/eks/latest/userguide/kro-troubleshooting.md b/eks/latest/userguide/kro-troubleshooting.md index ac5ab7b41..d26bdc81f 100644 --- a//eks/latest/userguide/kro-troubleshooting.md +++ b//eks/latest/userguide/kro-troubleshooting.md @@ -107 +107,2 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl describe <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> + kubectl describe custom-kind + my-instance @@ -110 +111 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get events --field-selector involvedObject.name=<replaceable>my-instance</replaceable> + kubectl get events --field-selector involvedObject.name=my-instance @@ -113 +114,2 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status.conditions}' + kubectl get custom-kind + my-instance -o jsonpath='{.status.conditions}' @@ -116 +118,2 @@ If custom resource instances exist but the underlying Kubernetes resources (Depl - kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status.state}' + kubectl get custom-kind + my-instance -o jsonpath='{.status.state}' @@ -179 +182 @@ CEL expression errors are caught at ResourceGraphDefinition creation time, not w - kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.status.conditions[?(@.type=="ResourceGraphAccepted")]}' + kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.status.conditions[?(@.type=="ResourceGraphAccepted")]}' @@ -182 +185,2 @@ CEL expression errors are caught at ResourceGraphDefinition creation time, not w - kubectl describe resourcegraphdefinition <replaceable>my-rgd</replaceable> + kubectl describe resourcegraphdefinition my-rgd + @@ -215 +219 @@ kro automatically infers dependencies from CEL expressions and creates resources - kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.status.topologicalOrder}' + kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.status.topologicalOrder}' @@ -223 +227,2 @@ This shows the computed order based on CEL expression references between resourc - kubectl get <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> -o jsonpath='{.status}' + kubectl get custom-kind + my-instance -o jsonpath='{.status}' @@ -226 +231 @@ This shows the computed order based on CEL expression references between resourc - kubectl get deployment <replaceable>my-deployment</replaceable> -o jsonpath='{.status.conditions}' + kubectl get deployment my-deployment -o jsonpath='{.status.conditions}' @@ -242 +247 @@ The `readyWhen` field is optional. If not specified, resources are considered re - kubectl get events -n <replaceable>namespace</replaceable> --sort-by='.lastTimestamp' + kubectl get events -n namespace --sort-by='.lastTimestamp' @@ -255 +260,2 @@ If instances fail to create due to schema validation errors, verify the instance - kubectl describe <replaceable>custom-kind</replaceable> <replaceable>my-instance</replaceable> | grep -A 5 "Validation" + kubectl describe custom-kind + my-instance | grep -A 5 "Validation" @@ -274 +280 @@ If instances fail to create due to schema validation errors, verify the instance - kubectl get resourcegraphdefinition <replaceable>my-rgd</replaceable> -o jsonpath='{.spec.schema}' + kubectl get resourcegraphdefinition my-rgd -o jsonpath='{.spec.schema}'