KubeZap Operator
github.com/kubezap/kubezap-operator- Category
- Developer Tools
- Rank
- No. 3013Tools index
Previous survey · No. 2735 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Workflow Automation
- Latest release
- v0.2.1
- Date
About
KubeZap is a Kubernetes operator for declarative, event-driven workflow automation defined as CRDs in YAML. Workflows trigger on webhooks, Kafka messages, cron schedules or Kubernetes resource events. Steps include HTTP calls, data transforms, conditional branching, timed waits and retry policies, with no web UI or proprietary runtime.
At a glance
KubeZap defines event-driven workflows as Kubernetes resources and records each execution as a FlowRun. It is worth trying when your automations already belong alongside cluster configuration and you want to inspect their results with Kubernetes tooling.
Good fit
Platform teams connecting a webhook, scheduled event or cluster change to a short sequence of API calls.
Consider something else when
Pass if workflow authors need a visual editor or you do not operate Kubernetes.
Start here
In a test namespace, wire a synthetic webhook to one harmless HTTP call. Make the test receiver fail once and check how the retry appears in the FlowRun.
Cost and requirements
The operator documents Kubernetes 1.27 or newer and requires permission to install its resource definitions and controller.
Limits to know
The security model separates the HTTP executor from Kubernetes secret access. You still need to scope controller access and check outbound destinations before a workflow uses real credentials.
Sources checked 2026-11-05. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.