kwd v0.2.1 · early development
Know if the rollout is ready
without squinting at kubectl
Tiny Go CLI that checks Kubernetes workload readiness with client-go. Single pass for cron and CI, or a daemon with Slack and HTTP probes.
Live traffic on gghstats · Cosign signed releases · MIT
Readiness without a monitoring stack. Declare the workloads. Get a verdict.
Built for operators who need a verdict now
One answer for cron and CI
interval 0 runs a single pass and exits 0 or 1. Wire it into jobs without standing up Prometheus first.
Same check path in the daemon
interval greater than 0 loops the identical readiness path, notifies on transitions, optional HTTP healthz and metrics.
client-go only
No kubectl binary on the PATH. Read only against the API. Distroless image and Cosign signed releases.
Config first
Declare deployments and statefulsets in YAML. Sample config and operator manifests ship beside the CLI.
How it works
- 01
Install
Homebrew, the get install script, a release tarball, or the GHCR image.
- 02
Declare refs
Print a sample profile, point kube context, list the workloads that matter.
- 03
Check or watch
Run once for CI, or leave the daemon up with Slack and probes.
Install
Primary path: Homebrew or the verified install script. ghcr.io/hrodrig/kwd:v0.2.1
Homebrew
brew install hrodrig/kwd/kwdOne liner (Linux / macOS)
curl -fsSL https://get.kwd.hermesrodriguez.com/install.sh | shOperator manifests · Contract: kwd-selfhosted · SPECIFICATIONS
FAQ
Is kwd ready for production as my only readiness gate?
Not yet. Until v1.0.0 treat it as early development. Use it to learn and complement existing signals, not as the sole production gate. Use at your own risk under the MIT License.
Which kinds are supported today?
deployment and statefulset. daemonset, service, and pvc are on the roadmap. The SPECIFICATIONS file describes the v0 target contract.
Does it need kubectl installed?
No. kwd talks to the API with client-go. You still need a valid kubeconfig or in cluster credentials.
How do notifications work?
Slack Incoming Webhooks today. Daemon mode alerts on overall ready to not ready transitions, with optional hysteresis and repeat while firing.
Where do I run it?
Bastion cron or systemd, docker run, or in cluster CronJob and Deployment. See kwd-selfhosted for operator notes and manifests.
How do I verify a release?
GitHub Releases ship Cosign signatures and SBOMs. The get install script can verify with cosign when available.
Get the binary. Point it at your refs.
Same install paths as above. Pre 1.0: evaluate before you trust it alone in production.
Install kwd