I am deploying a website with Rancher 2. The pods are spawning, accessible on the web. Ok.
I try to add a HTTPS support with Let’s Encrypt. I installed cert-managed from Helm. I created a ClusterIssuer, a Certificate. The Certificate describe :
Name: acme-crt Namespace: default Labels: <none> Annotations: <none> API Version: xxxxx/v1alpha1 Kind: Certificate Metadata: Cluster Name: Creation Timestamp: 2018-07-05T12:08:21Z Generation: 1 Resource Version: 779229 Self Link: xxxxx UID: xxxxxxxx Spec: Acme: Config: Domains: www.xxxx sub1.xxxx Http 01: Ingress: Ingress Class: nginx Common Name: Dns Names: www.xxx sub1.xxx Issuer Ref: Kind: ClusterIssuer Name: letsencrypt-issuer Secret Name: acme-crt-tls Status: Acme: Order: URL: xxxxxx Conditions: Last Transition Time: 2018-07-05T12:08:24Z Message: Order validated Reason: OrderValidated Status: False Type: ValidateFailed Last Transition Time: <nil> Message: Certificate issued successfully Reason: CertIssued Status: True Type: Ready Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal CreateOrder 27m cert-manager Created new ACME order, attempting validation... Normal IssueCert 27m cert-manager Issuing certificate... Normal CertObtained 27m cert-manager Obtained certificate from ACME server Normal CertIssued 27m cert-manager Certificate issued successfully
It seems to be ok ?
But when I go back to Rancher UI, on the Resources > Certificates page, it’s empty.
Any ideas ?