title: How can I run a Kubernetes pod with the sole purpose of running exec against it?
body: <p>Please before you comment or answer, this question is about a CLI program, not a service. Apparently 90% of Kubernetes has to do with running services, so there is sparse documentation for CLI programs meant to be part of a pipeline workflow.</p>
  
  <p>I have a command line program that uses stdout for JSON results.</p>
  
  <p>I have a docker image for the command line program.</p>
  
  <p>If I create the container as a Kubernetes Job, than stdout and stderr are mixed and require heuristic scrubbing to get pure JSON out.</p>
  
  <p>The stderr messages are from native libraries outside of my direct control.</p>
  
  <p>Supposedly, if I run <code>kubectl exec</code> against a running pod, I will get the normal stdout/stderr pipes.</p>
  
  <p>Is there a way to just have the pod running without an entrypoint (or some dummy service entrypoint) with the sole purpose of running <code>kubectl exec</code> against it?</p>