kubectl-neat VS kubeval

It depends on kubectl-neat mentioned in pre-requisites.

I if you are getting objects out in yaml i recomend you to use neat https://github.com/itaysk/kubectl-neat

Install [neat]((https://github.com/itaysk/kubectl-neat) plugin with krew :

Clean Now let’s talk about how you can use the "Clean" feature of ValidKube to clean and enhance your YAML files with an instant click. It's repository kubectl-neat is https://github.com/itaysk/kubectl-neat It works as shown in image below :-

The idea behind Validkube is to fuse together the capabilities of three other popular open-source projects (kubeval, kubectl-neat & trivy) and present them in a single view, providing users with a way to ensure YAML code hygiene and security, in one place, with just a few clicks of the button.

neat - possibly my favourite of all the plugins is neat which removes all the generated, redundant fields from YAML output of Kubernetes resources. If you're tired of scrolling through all the managedFields and other garbage, then definitely give this one a try.

There is a product that does this called kubectl-neat: https://github.com/itaysk/kubectl-neat

kubectl-neat (via Krew)

I don't use it myself, but it seems what are you looking for. https://github.com/instrumenta/kubeval

1. Validate Using ValidKube, you can Validate your YAML files. It can help you fix the indentation also add, remove and rearrange things according to the actual YAML and Kubernetes schema. It is available as a open source repository as Kubeval . https://github.com/instrumenta/kubeval

The idea behind Validkube is to fuse together the capabilities of three other popular open-source projects (kubeval, kubectl-neat & trivy) and present them in a single view, providing users with a way to ensure YAML code hygiene and security, in one place, with just a few clicks of the button.

Kubeval - Well known, It only validates against the given Kubernetes Version but doesn’t provide a migration path

Kubeval and kubeconform are command-line tools that were developed with the intent to validate Kubernetes manifests without the requirement of having a running Kubernetes environment. Because kubeconform is based on kubeval, they operate similarly — verification is performed against pre-generated JSON schemas that are created from the OpenAPI specifications (swagger.json) for each particular Kubernetes version. All that remains to run the schema validation tests is to point the tool executable to a single manifest, directory or pattern.