cert-manager: Current master version fails to request certificate
/kind bug
I tried using the master version to get a certificate from letsencrypt (staging and prod), and my Certificate resource never gets any events, the http challenge is never checked, and the secret is never created.
Doing the same on v0.2.3 works as documented.
Environment:
-
Kubernetes version (use
kubectl version): Client Version: version.Info{Major:“1”, Minor:“8”, GitVersion:“v1.8.6”, GitCommit:“6260bb08c46c31eea6cb538b34a9ceb3e406689c”, GitTreeState:“clean”, BuildDate:“2017-12-21T06:34:11Z”, GoVersion:“go1.8.3”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“9+”, GitVersion:“v1.9.2-gke.1”, GitCommit:“4ce7af72d8d343ea2f7680348852db641ff573af”, GitTreeState:“clean”, BuildDate:“2018-01-31T22:30:55Z”, GoVersion:“go1.9.2b4”, Compiler:“gc”, Platform:“linux/amd64”} -
Cloud provider or hardware configuration**: GCP
-
Install tools: Helm
-
Others: I set up cert-manager using instructions from this tutorial: https://github.com/ahmetb/gke-letsencrypt
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 18 (3 by maintainers)
@ipedrazas Thank you! I spent days trying to figure out why I wasn’t get a certificate and adding configmaps to the clusterrole fixed it.
Also getting the same issue. I’ve tried using
canaryandmaster-3666but still getting the same problem with both buildsI ran in the same issue today and using the image master-3666 solved