<p>I setup up a prototype cluster in Azure Kubernetes Service to test the ability to configure HTTPS ingress with cert-manager. I was able to make everything work, now I'm ready to setup my production environment.</p>

<p>The problem is I used the sub domain name I needed (sub.domain.com) on the prototype and now I can't seem to make Let's Encrypt give a certificate to the production cluster.</p>

<p>I'm still very new to Kubernetes and I can't seem to find a way to export or move the certificate from one to the other.</p>

<p><strong>Update:</strong></p>

<p>It appears that the solution provided below would have worked, but it came down to needing to suspend/turnoff the prototype's virtual machine. Within a couple minutes the production environment picked up the certificate.</p>

Ian
<p>you can just do something like:</p>

<pre><code>kubectl get secret -o yaml
</code></pre>

<p>and just copy\paste your certificate secret to a new cluster, or use something like heptio ark to do backup\restore.</p>

<p>ps. I dont know why it wouldn't let you create a new cert, at worst you would need to wait 7 days for your rate limit to refresh.</p>
