You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
Describe the bug
is there a way we can get the K8s Object names which are reported during k8s schema validation.
To Reproduce
Steps to reproduce the behavior:
using kustomize with lot of crds and yamls.
datree kustomize test Expected behavior
k8s object name should be printed in the error message. As we use buch of CRD files and yamls it was quite difficult to find which object has that null value for creationtimestamp
Screenshots
Desktop (please complete the following information):
Datree version (run datree version):
-1.8.21
Additional context
Add any other context about the problem here.
If possible, include a YAML file to reproduce the bug.
The text was updated successfully, but these errors were encountered:
that's a good point.
which metadata do you think can help you debug schema validation errors?
will name and kind be enough?
in the meanwhile, as a workaround, you can use the --save-rendered flag.
this way, you can open the rendered manifest to understand the root cause of the schema validation error:
Thanks. we havily use kustomize with many crds etc. object name/kind will help us lot in identifying the incorrect object. we are not saving rendered output in our CI pipeline. at present we are doing a manual check in the repo.
Hello @Mahesh-Gunda-Maersk, I totally agree with your feedback. We're using Kubeconform for validating the K8s schema, and this ability already exists in this package.
I'm moving this issue to up for grabs, so someone can raise a PR to support this one. thanks!
Describe the bug
is there a way we can get the K8s Object names which are reported during k8s schema validation.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
k8s object name should be printed in the error message. As we use buch of CRD files and yamls it was quite difficult to find which object has that null value for creationtimestamp
Screenshots
Desktop (please complete the following information):
Datree version (run
datree version
):-1.8.21
Additional context
Add any other context about the problem here.
If possible, include a YAML file to reproduce the bug.
The text was updated successfully, but these errors were encountered: