Cert-manager and let's encrypt

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: *.intash.orbitbi.com

I ran this command: we have clusterissuer created and cert-manager makes use of clusterissuer to get the certificates for each namespace in the kubernetes cluster.

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is: Godaddy

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

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):

Earlier cert-manager had created certificates for [orbitcert01.intash.orbitbi.com][orbitcert02.intash.orbitbi.com]
[orbitcert03.intash.orbitbi.com] but these applications doesn't exist now ,we had deleted them a month ago and certificates also doesn't exist in our cluster but I get notification emails from let's encrypt that for the above mentioned certificates will be expired in few days and make sure we renew them.

Though certificates or resources doesn't exist in the kubernetes cluster is let's encrypt storing the certificates it issued already?

LE stores all the information about recently issued certs.
That is how it knows if/when to send expiry emails.
If you have removed those certs, then it stands to reason that you haven't (and won't) renew them.
And that explains why LE is sending expiry emails about them.
Since you are aware of their situation, you can ignore emails about those certs.

2 Likes