crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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 <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2025-08-07 20:55:46 -07:00
parent 4efb03c1fe
commit fcba82541c
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
content/master/operations/operation.md
View File

@ -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
```