Description of problem

With docker, it was pretty normal to end up with kata-runtime in your PATH, and thus use of kata-runtime kata-env was quite common, and useful when debugging.

With the advent of multiple runtime variants (kata-runtime, kata-qemu, kata-fc and kata-nemu), and with the more common use of k8s, it is getting harder to work out which kata-esque runtime might be in play, where its binaries live (and they could be different for each node of a cluster?), and how they are configured...

It might be nice to see if we can construct some form of kata-k8s-env.sh script that will probably use a bunch of kubectl get trickery and some JSON munging to generate us a nice report about how a k8s cluster is or is not set up with Kata.

I may be slightly biased, as I'd quite like to get this information to store alongside any k8s automatic metrics measures we take, like we do for docker metrics already.

Open to ideas here...