kubepug VS kubeval

Agreed. The tooling around upgrades is painfully atrocious, and stuff like kubepug [1] should be part of the Kubernetes core.

[1] https://github.com/kubepug/kubepug

Not strictly related to security, but I find kubepug awesome when planning upgrades, especially if you need to jump across 2 or 3 major versions.

Also kubepug - https://github.com/rikatz/kubepug

References Kubepug net-forward Krew

Verify with a tool like kubepug, something like

kube-pug - is a plugin known as deprecations in krew. Every cluster needs to be upgraded sooner or later and at some point you will run into API deprecations and/or removals. Finding what's being deprecated can be long and error-prone process and this plugin tries to simplify that. All you need to do is run kubectl deprecations --k8s-version=v1.XX.X and you will get list of all the instances of API objects in cluster that will be deprecated or removed in the specified version.

Kubepug - Only checks whether the existing objects have any Deprecated ApiVersions

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.