gitops-catalog VS kubectl-neat

You can reference a remote repository as a base. I pull in a lot of content directly from https://github.com/redhat-cop/gitops-catalog, referencing either the commit hash or tag in the URL, for operator management.

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)