cert-manager: message: Certificate does not exist
Describe the bug: cert-manager is up and running, but it does not issue certificates for the domain
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
clusterName: ""
creationTimestamp: 2019-02-07T16:45:40Z
generation: 1
name: custom-crt
namespace: default
...
spec:
acme:
config:
- domains:
- custom.mydomain.com
http01:
ingress: ""
ingressClass: nginx
dnsNames:
- custom.mydomain.com
issuerRef:
kind: ClusterIssuer
name: letsencrypt-staging
secretName: custom-crt
status:
conditions:
- lastTransitionTime: 2019-02-07T16:45:40Z
message: Certificate does not exist
reason: NotFound
status: "False"
type: Ready
Webhook certificates looks ok
Expected behaviour: Certificate should be ready and “status: True”
Steps to reproduce the bug: Follow quickstart guide
Anything else we need to know?:
Environment details::
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T10:09:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.12-gke.1", GitCommit:"8c6cac7466d8b36ead34f89822e37eb6e4e011c8", GitTreeState:"clean", BuildDate:"2019-01-15T19:48:39Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
- Cloud-provider/provisioner GKE
- cert-manager version: (v0.6.0
- Helm stable
/kind bug
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 16
- Comments: 26 (2 by maintainers)
Same issue here
Certificate config
Generated Certificate resource
The
ca.crtandtls.crtare empty:cert-manager controller logs
Anybody have a fix for this? I have the same issue.
I was got the same error. when i checked
cert-managerlogs usekb logs cert-manager-xxxxxxxxxx-xxxxx, and i got as follow:I was made too many certificates issued, so i resolved it by waiting sometimes and try again.
Could you provide the output of
kubectl describe clusterissuer,certificate,order,challenge?As well as logs from cert-manager 😄
/triage support
I encountered about 20 different ways the dns01 certificate could fail
kubectl describe clusterissuer,certificate,order,challenge --all-namespaces=trueand live reading the cert-manager pod logs helped me fix them.