You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed kube-cert-manager from the tip of master branch today and configured with my cloudflare API key. Output from the kcm pod shows healthy status:
$ kubectl logs -f kube-cert-manager-2773976669-52w89 kube-cert-manager
2017/04/24 20:39:02 Starting Kubernetes Certificate Controller...
2017/04/24 20:39:02 Kubernetes Certificate Controller started successfully.
2017/04/24 20:39:02 Watching certificates and ingresses in all namespaces
Before started pod, I did kubectl apply -f k8s/certificate-type.yaml.
Then I did kubectl apply for a Certificate resource as follows:
I'm also having this problem-- unfortunately switching to v0.4.0 isn't an option for me, because I need support for SANs which appears to only be in the master branch.
I have deployed kube-cert-manager from the tip of master branch today and configured with my cloudflare API key. Output from the kcm pod shows healthy status:
Before started pod, I did
kubectl apply -f k8s/certificate-type.yaml
.Then I did
kubectl apply
for a Certificate resource as follows:However I don't see any of the logs about this Certificate getting picked up (like the sample output in https://github.com/PalmStoneGames/kube-cert-manager/blob/master/docs/create-a-certificate.md).
No secrets are created either so it probably doesn’t work.
But the certificate resource is there:
Restarting does not help. I am basically stuck at this point.
The text was updated successfully, but these errors were encountered: