<p>I have an entrypoint defined in my container image, and it runs before the args specified in my deployment manifest, as it should.  But when I execute a command on that container using <code>kubectl exec</code>, it seems to bypass the container entrypoint.  Is this the expected behavior?  Can I somehow force it to always use the entrypoint commands?</p>

<p>That's expected. If you really want what's in the <code>entrypoint.sh</code> you can do something like this:</p>
<pre><code>kubectl exec -it &lt;pod-name&gt; -c &lt;container-name&gt; -- /path/to/entrypoint.sh
</code></pre>
<p>Hope it helps!</p>
