I am using cert-manager in my kubernetes cluster on IBM Cloud.
When I was configuring for the first time, I made a few mistakes, but my domain now runs fine on https.
However my server logs mention that there are still some acme-challenges http calls being made to the server resulting in 404 and they are irrelevant. It has been happening for over 2 months now.
Yes, that's cert-manager's preflight request. This means there's some open Certificate resource which includes that domain, which continues trying to fulfill itself.
You should be able to locate the offending Certificate resource using kubectl or the Kubernetes web interface and delete it.
➜ kubectl get CertificateRequest --all-namespaces
NAMESPACE NAME READY AGE
istio-system ingress-cert-3740439329 True 17d
➜ kubectl get Order --all-namespaces
NAMESPACE NAME STATE AGE
istio-system ingress-cert-3740439329-276182855 valid 17d
➜ kubectl get Challenge --all-namespaces
No resources found