<p>I use kube-lego in 0.1.5-a9592932 version, but this service are deprecated and now the time has come for migrate for cert-manger. When testing migrate I lost the secret &quot;kube-lego-account&quot;, but I need this! It's possible forcing generate the secret? I restarted the kube-lego and check the logs and found this:</p>
<pre><code>Attempting to create new secret&quot; context=secret name=kube-lego-account namespace=default
</code></pre>
<p>But the secret not was created. How can I do to solve this issue?</p>

roliveira
<p>let's take an another path, Letsencrypt official docs say that they won't be supporting any longer for below 0.8 versions, so I recommend you to install cert-manager provided by Jetstack, that you can find <a href="https://cert-manager.io/docs/installation/kubernetes/" rel="nofollow noreferrer">here</a>, to install the helm chart for it.</p>
<p>The follow <a href="https://stackoverflow.com/questions/58423312/how-do-i-test-a-clusterissuer-solver/58436097?noredirect=1#comment103215785_58436097">this stackoverflow post</a>, for configurations, note that if the api version mentioned in that post doesn't support in case of cluster issuer, then rather use</p>
<pre><code>apiVersion: cert-manager.io/v1alpha2
</code></pre>
<p>Note that , the tls secret name mentioned in the certificate will be auto-generated by cert-manager, and it automatically starts an acme-challenge to validate the domain, once you patch that secret name to the TLS in your ingress rule.</p>
<p>It shall solve the issue and the certificate's status will change to ready after the domain verification</p>
