Bugs and features can be opened in the project GitHub repository. All tickets will be answered within three working days max.
Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. Instead, we recommend using "Discussions" to ask support-related questions.
Yes. Datree also has a Helm plugin that can be accessed through the helm CLI, to provide a seamless experience to Helm users.
You should always inspire to "shift-left" any validation process. This way, the end-user (e.g. a developer) can receive feedback as soon as possible without the cost of context switching. With Datree, the validation process can start at the CI (and even earlier), instead of waiting for the CD.
Also, the kubectl validation process does not always have a clear-cut error message when failing. This can create confusion for the end-user about what he should fix and how. With Datree, the Kubernetes owner can control the error message and instruct the end-user the appropriate action to take
To conclude, the best practice is to run Datree's policy check before any kubectl validation check.
No, but this is on our roadmap. If you want to join our preview community and be part of our Early Adopter Community, send an email to firstname.lastname@example.org.
This functionality is still in beta and only available to accounts in our Early Adopter Community.
No, although we are looking to build an on-premise version of the Dashboard for use in private clouds.
Datree evaluates your policy in the cloud against the data provided, in an encrypted way, similar to how your workloads operate in the cloud. The data is sent only after processing and not in its raw format. We send the properties of the manifest so we can run the policy and verify it passes. All the data is sent encrypted, it's encrypted in our database and no one has access to it.