<p>I have a kubernetes cluster setup,
I am converting a docker-compose using komposer , and I get:</p>
<pre><code>WARN Volume mount on the host &quot;&lt;SOME_PATH&gt;&quot; isn't supported - ignoring path on the host
WARN Volume mount on the host &quot;&lt;SOME_PATH_2&gt;&quot; isn't supported - ignoring path on the host
WARN Volume mount on the host &quot;&lt;SOME_PATH_3&gt;&quot; isn't supported - ignoring path on the host
</code></pre>
<p>we built a docker-compose that uses volume mounts for key,crt files and that looks like volumes are not supported by K8.</p>
<p>I found this : <a href="https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/</a>
and it looks like Kubernetes can make and renew its own certs. That's great.
How do I get access to those certs so I can use them in my Koa/Nodejs microservice?
or is there another standard way to apply certs at the application layer?</p>
<p>There was some talk about if this didn't work to move to nginx or Kong and let that use certs.
I'm trying to see if there's an application layer way to do this rather than go that route.
Any suggestions or comments are appreciated.</p>
<p>EDIT: it seems I can assign a cert to a secret and call it via my application? I'm new to kubernetes so... I may be looking into this.</p>

<blockquote>
<p>or is there another standard way to apply certs at the application layer?</p>
</blockquote>
<p>Yes, for TLS and mTLS between applications within your cluster, I would consider to use a <em>service mesh</em>, e.g. <a href="https://istio.io/latest/docs/tasks/security/authentication/authn-policy/#auto-mutual-tls" rel="nofollow noreferrer">Istio (with mTLS)</a> or <a href="https://linkerd.io/2/features/automatic-mtls/" rel="nofollow noreferrer">Linkerd (with mTLS)</a>. With a <em>service mesh</em> you get TLS encryption managed for you, between Pod to Pod - but your application does not need to manage any certificates.</p>
