-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schema Recognition issue in kubeconform v0.6.3 and above #247
Comments
I'm pretty sure I run into the same issue
validates all the usual CRDs & ExternalSecrets, but I was unable to add other CRDs. Apparently, only 1 additional |
We solved this issue by providing a folder of Schemas for the
|
Hi @michaelholtermann , the -schema-location is meant to be used not as a path to a particular file, but as a templated string, see documentation at https://github.com/yannh/kubeconform?tab=readme-ov-file#overriding-schemas-location Especially: "if the -schema-location value ends with .json - Kubeconform assumes the value is a Go templated string that indicates how to search for JSON schemas." You're not the first one to trip on the usability of this feature unfortunately 😬 Glad you found a solution! |
The issue still persist. Certainly there is an issue with the CRD but we didn't find a way to fix it. Is there a way to find out, why the CRD that was found was rejected by kubeconform?
You will find below the files to reproduce the regression we are observing. |
Hello,
I am experiencing a schema recognition issue with kubeconform starting from version 0.6.3 and continuing in the latest version 0.6.4.
The tool fails to recognize the schema for Apigee resources (ApigeeEnvironment and ApigeeOrganization):
Actual Results:
kubeconform versions 0.6.3 and 0.6.4 fail to recognize the schema for these resources, resulting in validation error:
The ApigeeOrganization CRD:
Expected Results:
kubeconform should correctly recognize and validate the schema of the given resource, as it did in version 0.6.2
I add Apigee Organization and Apigee Environment json schema generated
Apigee Organization:
Apigee Environment:
The text was updated successfully, but these errors were encountered: