<p>An existing nginx ingress named <code>nginx-proxy</code> running on the K8 cluster.</p>
<p>Now, there is a requirement from the Dev team to disable TLS 1.0, 1.1 support.</p>
<p>Upon searching, I could see <a href="https://kubernetes.github.io/ingress-nginx/user-guide/tls/" rel="nofollow noreferrer">this solution</a> using configmap.</p>
<p>Do you think applying/creating a new configmap as follows to an existing nginx ingress helps me to resolve the issue?</p>
<pre><code>kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-proxy
data:
  ssl-protocols: &quot;TLSv1.2 TLSv1.3&quot;
</code></pre>
<p>Adding a new configmap like that to an existing nginx ingress breaks anything?. Because this is for the production website.</p>
<p>A piece of advice would be really helpful.</p>

<p>You can follow this official document or disabling the TLS 1.0</p>
<pre><code>kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
data:
  ssl-ciphers: &quot;ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384&quot;
  ssl-protocols: &quot;TLSv1.2 TLSv1.3&quot;
</code></pre>
<p>You need to update the ciphers also as perversion instead of using the default one.</p>
<p>You can try with the above <strong>configmap</strong>.</p>
<p>Also, I would recommend updating the SSL/TLS cert if you using in ingress.</p>
<p>If you are using the cert-manager please try deleting the secret which containing the SSL/TLS cert for ingress endpoint and try getting the cert again using the cert-manager once.</p>
