feat: embed kubeconform schemas - #12
Merged
Merged
Conversation
Signed-off-by: Ilya Drey <ilya.drey@flant.com>
drey
force-pushed
the
feat/bump-nelm-version
branch
from
July 31, 2026 17:05
cf2fd79 to
6ffe272
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resource validation with kubeconform may not depend on network any more. Kubernetes standard resources and CRDs validation schemas are embedded into the binary. This feature become possible because of werf/nelm#673
We do use https://github.com/yannh/kubernetes-json-schema as a source for Kubernetes standard resources and https://github.com/datreeio/CRDs-catalog for the CRDs.