Multiple JSON via stdin only validates the first one

$ echo '{"kind":"Namespace","apiVersion":"v1","metadata":{"name":"test"}}\n{"kind":"Service","apiVersion":"v1","metadata":{"name":"test","namespace":"test"},"spec":{"ports":[{"name":"http","protocol":"TCP","port":80,"targetPort":80}],"selector":{"app":"test"},"type":"ClusterIP","sessionAffinity":"None"}}' | kubeval
The document stdin contains a valid Namespace

Start by reproducing the reported kubeval command and trace the stdin input path that handles multiple JSON documents. Done means the command validates both the Namespace and Service documents rather than only the first one.

Written by the indexing model from the issue text.