Datree monitors and validates your objects against your configured policy upon pushing them into a cluster, by using an admission webhook.
Datree will catch
edit operations and initiate a policy check against the configs associated with each operation.
After installation, Datree runs with enforcement mode disabled by default. To enable enforcement mode, see the behavior page.
If any misconfigurations are found and enforcement mode is enabled, the webhook will reject the operation and display a detailed output with instructions on how to resolve each misconfiguration.
Kubernetes uses different abstractions to simplify and automate complex processes. For example, when explicitly applying an object type
Deployment, under the hood, Kubernetes will “translate” this object into implicit objects of types
When installed on your cluster, other policy enforcement tools will validate both explicit and implicit objects. This approach may create a lot of noise and false positive failures since it will cause the webhook to validate objects that the users don’t manage and, in some cases, are not even accessible.
To avoid such issues, we decided to support the following triggers:
- Kubectl - validate objects that were created or updated using kubectl
applycommands. Objects that were implicitly created (e.g., pods created via deployment) are ignored since the webhook validates the deployment that generated them and is accessible to the user.
- Helm/Kustomize - validate objects that were created or updated using Helm or Kustomize.
- Gitops CD tools - validate objects that were explicitly created and distinguish them from other objects (custom resources) that were implicitly created during the installation and are required for the ongoing operation of these tools (e.g., ArgoCD, FluxCD, etc.)