From fcba82541c624392e8c6511b897da35630b9068a Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Thu, 7 Aug 2025 20:55:46 -0700 Subject: [PATCH] Add troubleshooting item about --enable-operations flag Added a new troubleshooting item to operation.md documenting the common error when Operations feature is not enabled and how to resolve it by adding the --enable-operations flag to Crossplane's startup arguments. Updated numbering for subsequent troubleshooting items accordingly. Signed-off-by: Nic Cope --- content/master/operations/operation.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/content/master/operations/operation.md b/content/master/operations/operation.md index 1b1c83c1..afae5a30 100644 --- a/content/master/operations/operation.md +++ b/content/master/operations/operation.md @@ -417,7 +417,14 @@ kubectl describe operation my-operation **Common failure scenarios:** -1. **ValidPipeline condition is False** - Function doesn't support operations: +1. **Operations do nothing** - Operations feature not enabled: + ```yaml + # Operation exists but has no status conditions and never progresses + status: {} + ``` + *Solution*: enable Operations by adding `--enable-operations` to Crossplane's startup arguments. + +2. **ValidPipeline condition is False** - Function doesn't support operations: ```yaml conditions: - type: ValidPipeline @@ -427,7 +434,7 @@ kubectl describe operation my-operation ``` *Solution*: use a function that declares `operation` capability. -2. **Succeeded condition is False** - Function run failed: +3. **Succeeded condition is False** - Function run failed: ```yaml conditions: - type: Succeeded @@ -437,7 +444,7 @@ kubectl describe operation my-operation ``` *Solution*: view function logs and fix the underlying issue. -3. **Resource apply failures** - View events for details: +4. **Resource apply failures** - View events for details: ```shell kubectl get events --field-selector involvedObject.name=my-operation ```