Migrate to kubeconform for k8s linting, as kubeval is now deprecated #420
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.
As per https://github.com/instrumenta/kubeval/blob/master/README.md -
kubeval
is deprecated, and the recommended replacement is kubeconform.This PR replaces our use of
kubeval
in the CIk8s-lint
step withkubeconform
.Implementation is done using the
helm plugin
provided here https://github.com/jtyr/kubeconform-helm.Justification for moving, aside from the deprecation, is the likes of #401 - where we could potentially add the use of 3rd party
k8s
modules(?), likecert-manager
.kubeconform
makes it very easy to validate these 3rd party additions by simply passinghttps://raw.githubusercontent.com/datreeio/CRDs-catalog/main/{{.Group}}/{{.ResourceKind}}_{{.ResourceAPIVersion}}.json
as a schema location