Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I’ve been trying to get Cert Manager working on Kubernetes. After having countless issues with ingress and HTTP01 challenges (I ran into this issue : https://stackoverflow.com/questions/61797014/error-broken-header-get-well-known-acme-challeng-with-letsencrypt-on-kuberna) , It looks like the next step is to try DNS01 resolution instead of HTTP .
I tried changing to the digialocean supported DNS resolution , but now came across the challenge failing via multiple cases of the following :
cert-manager Error presenting challenge: GET https://api.digitalocean.com/v2/domains/gapcm.com/records: 404 (request “419c6f10-c4b2-4281-a0f3-341e9eb3fb80”) Resource not found
My Domain is bought from and DNS records with Godaddy . It looks like I’d need to at that point find a Godaddy specific DNS01 Challenge Resolution method (Which isn’t supported by Cert-manager https://github.com/jetstack/cert-manager/issues/1083 , so probably not) or it seems like I’d need to transfer DNS records (And I assume the Domain Services itself) to digitalocean , which is also a probably not (Because our company has many Domans and Email services through godaddy) .
Can someone confirm this to me, or let me know if there’s a way to fix any of the above issues. Ideally HTTP01 would just work . I shouldn’t have to have 200+ (not an overstatement) tabs of research and 6+ straight days of debugging to migrate my docker-compose app to Kubuernetes .
72e571841e7f4a6881090a2f3e93c0
1txm05v1txm05v
jazzybruno
jazzybruno
1c73a43cf7ab4e9cb7f9e551f34a5e
Server Enthusiast
Sean DesPortes
Robin van der Knaap
4a0d624689d3431099e1b568c03569
Tomy Hsieh
Marek
BIdhan Bastola