<p>I'm trying to apply SSL to my kubernetes clusters (production &amp; staging environment), but for now only on staging. I successfully installed the cert-manager, and since I have a 5 subdomains, I want to use wildcards, so I want to configure it with dns01. The problem is, we us GoDaddy for DNS management, but it's currently not supported (I think) by cert-manager. There is an issue (<a href="https://github.com/jetstack/cert-manager/issues/1083" rel="noreferrer">https://github.com/jetstack/cert-manager/issues/1083</a>) and also a PR to support this, but I was wondering if there is a workaround for this to use godaddy with cert-manager since there is not a lot of activity on this subject? I want to use ACME so I can use let's encrypt for certificates.</p>

<p>I'm fairly new to kubernetes, so if I missed something let me know. </p>

<p>Is it possible to use let's encrypt with other type of issuers than ACME? Is there any other way where I can use GoDaddy DNS &amp; let's encrypt with kubernetes?</p>

<p>For now I don't have any Ingresses but only 2 services that are external faced. One frontend and one API gateway as LoadBalancer services.</p>

<p>Thanks in advance!</p>

<p>The accepted solution does work -- a different issuer is one way to go.  Though if you want to use the ACME issuer, you'll need to solve challenges.  This can be done via either a <a href="https://cert-manager.io/docs/configuration/acme/http01/" rel="nofollow noreferrer">HTTP01</a> solver or a <a href="https://cert-manager.io/docs/configuration/acme/dns01/" rel="nofollow noreferrer">DNS01</a> solver.  If you choose to go with the DNS01 solver, you'll either need:</p>
<ol>
<li>to move your DNS hosting from GoDaddy to one of the supported <a href="https://cert-manager.io/docs/configuration/acme/dns01/#supported-dns01-providers" rel="nofollow noreferrer">providers</a>.</li>
<li>or you can try using this GoDaddy Webhook <a href="https://github.com/snowdrop/godaddy-webhook" rel="nofollow noreferrer">provider</a>, which you may already be aware of.  Though I can't guarantee that the project is in working status.</li>
</ol>
