If a configuration is missing 'apiversion', 'type', etc, keys, kubeval dumps the issue to log.Error, prints null, and exits.
When the -o flag is specified as json, I would expect kueval to report the error in json format.
It looks like if apiversion or type aren't specified, it isn't possible to build the URL to download the appropriate schema. So kubeval fails fast and makes these checks before even testing against the schema
If a configuration is missing 'apiversion', 'type', etc, keys, kubeval dumps the issue to log.Error, prints null, and exits. When the -o flag is specified as json, I would expect kueval to report the error in json format.
Example
Current output:
Possible JSON output: