K8s Cert manager keeps giving : Issuing certificate as Secret does not exist

[nzainabmlab]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: backend.wearthat.me

I ran this command: I followed this tutorial Install cert-manager to setup SSL with Let’s Encrypt and Cloudflare DNS with automatic renewal before your SSL expire in Kubernetes | by Paris Nakita Kejser | DevOps Engineer, Software Architect and Software Developering | Medium. I tried cert manager versions v1.4, v1.7, v1.10

It produced this output: my certificate is never ready

My web server is (include version): Digital ocean

The operating system my web server runs on is (include version): Django

My hosting provider, if applicable, is: DNS provider is cloudflare

I can login to a root shell on my machine (yes or no, or I don't know): I can login to kubectl shell

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

[griffin]

Welcome to the Let's Encrypt Community!

The usual reason for a certificate not being acquired by cert-manager is lack of application of an ingress manifest specifying the host for the certificate. I do see that step though in the tutorial you linked. Please post the log from cert-manager. It will greatly aid with debugging.

In my corporate experience with cert-manager I have never needed to create or apply a yaml file for the certificate itself since cert-manager generates and populates the k8s secret containing the certificate. I have used ingress-nginx there though.

Tutorials