AWK never stops to show its usefulness.

At work a colleague of mine was looking for some nice way to get some summary of configured/created resources from a kubectly apply with dry run.

I stepped in and provided an awk one-liner that counts and collects the configured and created resources, suppressing the various unchanged one...

Suddenly we were able to clearly see what our kubectl apply were going to touch :)