Inspiration
Debugging in k8s environment is complex. In most cases the issues are related to configuration of manifests, therefore validating the inputs in manifest before hand should be a good practice. Datree is one such tool that allows designers to write policies to validate the manifest. Our idea is to use this Policy as code to extend it to follow the deployment best practices like terminationPolicies to avoid production surprises.
What it does
It uses the Datree tool to validate certain k8s attributes which are must have to debug the cluster in minimum time and cost.
How we built it
We have build it using the datree json and yaml schema , where we used the underlying Datree functionality to validate our k8s before deployments.
Challenges we ran into
Initially, since the tool is very new to us, we struggled alot to write complex policies but with the help of datree engineers demo and minimal understanding of go we were able to make it.
Accomplishments that we're proud of
Major accomplishments are:
- Being able to validate the manifest against custom policies,
- Understanding the underlying Datree architecture and how it works,
- At the end of the day, the courage we accomplish to complete the planned work , it feels great.
## What we learned
Learned to debug the k8s manifest.
Prior manifest validation can reduce the change of errors.
## What's next for Custom Policies using Datree I would like to see Datree integration with open-source k8s workflows to catch required custom policies before the code is merged.
Log in or sign up for Devpost to join the conversation.