Show HN: KubeZap – Declarative workflow automation for Kubernetes

Show HN: KubeZap – Declarative workflow automation for Kubernetes Define event-driven automations as CRDs — no web UI, no proprietary runtime, no vendor lock-in. Trigger on webhooks, Kafka messages, cron schedules, or Kubernetes resource events.

This PolicyChange is relevant to the technology intelligence record because it involves GitHub, Meta, Kubernetes, Docker. The source article should remain the factual reference for follow-up coverage.

• Define event-driven automations as CRDs — no web UI, no proprietary runtime, no vendor lock-in.
• Trigger on webhooks, Kafka messages, cron schedules, or Kubernetes resource events.
• Execute multi-step flows with HTTP calls, data transforms, conditional branching, timed waits, and retry policies — all declared in YAML and version-controlled alongside your infrastructure.
• Why KubeZap Credentials never leave the cluster's trust boundary.
• The controller resolves secrets in-memory and hands a fully-substituted request to a dedicated, low-privilege HTTP executor pod — no Kubernetes API access, no secrets RBAC, independent SSRF protection.
• Your API keys are never written to etcd and never stored in a separate workflow database.