datree: Manifest Policy Checks (Deprecated)
datree test ran schema validation plus policy checks on Kubernetes manifests, but Datree was discontinued; use kubeconform with kube-score, Polaris, or KubeLinter instead.
Datree combined manifest validation and best-practice policy in one CLI, with a hosted policy dashboard. The product was shut down, so this page exists to help you recognize and replace datree steps in inherited pipelines.
What it does
datree test validated manifests against Kubernetes schemas and evaluated a set of built-in and custom policies, reporting rule violations. It offered an offline mode, but its default flow relied on a hosted backend that no longer exists.
Common usage
# legacy invocation
datree test deployment.yaml
# offline mode used in air-gapped CI
datree test deployment.yaml --offline local
# modern replacements (validation + best practices)
kubeconform -summary -strict deployment.yaml
kube-score score deployment.yamlOptions
| Flag | What it does |
|---|---|
| <path> | Manifest file, directory, or glob to test |
| --offline <mode> | Run without the hosted backend (local) |
| -o, --output <fmt> | Output format: json, yaml, xml, JUnit, simple |
| --only-k8s-files | Restrict to files that look like Kubernetes manifests |
Migration and CI
Because the Datree service is gone, jobs that call datree without --offline can hang or fail contacting the backend. Split its two jobs across maintained tools: kubeconform for schema validation and kube-score, Polaris, or KubeLinter for best-practice policy. For Rego-style custom rules, conftest or Kyverno CLI cover the gap.
Common errors in CI
"command not found: datree" on refreshed runner images signals the tool was removed; do not reinstall it, migrate off. Network timeouts or "failed to send report" errors come from the retired hosted backend. If a legacy step still runs, force --offline local to avoid the dead API, then plan the replacement.