<p>As part of compliance efforts seems like we need to use the Ingress Certificates directly being mounted in Memory , using emptyDir with <code>medium:Memory</code> ,but I am not able to find any examples in Nginx Ingress Controller repo or otherwise on how to do so .
If any one has done this before , please provide some insights .</p>

tushar_sappal
<p>I had never done this. Just tried and all worked fine. I had to put the certs manually though. I mean,I created a debian pod and installed everything manually. I don't know how are you going to do that part so it will be elegant.</p>
<p>Anyways, this is the yaml that worked for me with self signed certs for <a href="http://www.example.com" rel="nofollow noreferrer">www.example.com</a>.</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: nginx-https
  labels:
    app: nginx
spec:
  containers:
  - image: debian
    name: nginx
    volumeMounts:
    - mountPath: /etc/nginx/certs
      name: certs
    tty: true
  volumes:
  - name: certs
    emptyDir:
      medium: &quot;Memory&quot;
</code></pre>
<p>And the request</p>
<pre><code>curl -vvv https://service -k
...
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=www.example.com; O=example organization
*  start date: Jan 18 15:48:22 2021 GMT
*  expire date: Jan 18 15:48:22 2022 GMT
*  issuer: O=domain Inc.; CN=example.com
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
&gt; GET / HTTP/1.1
&gt; Host: 192.168.31.62
&gt; User-Agent: curl/7.59.0
&gt; Accept: */*
&gt; 
&lt; HTTP/1.1 200 OK
&lt; Server: nginx/1.14.2
&lt; Date: Mon, 18 Jan 2021 15:52:41 GMT
&lt; Content-Type: text/html
&lt; Content-Length: 612
...
</code></pre>
