Check the API with cmctl

Check that the cert-manager API is ready, using the cmctl CLI

cmctl check api

tool
cert-manager16 commands
tags
cert-managertlscmctlcli

More cert-manager commands

  • kubectl apply -f - <<EOF apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: letsencrypt-prod spec: acme: server: https://acme-v02.api.letsencrypt.org/directory email: admin@example.com privateKeySecretRef: name: letsencrypt-prod solvers: - http01: ingress: class: nginx EOF

    Create a production Let's Encrypt ClusterIssuer with the HTTP-01 solver

  • cmctl renew <name> -n <ns>

    Reissue the certificate now without waiting for the renewal window; a new CertificateRequest will appear

  • cmctl status certificate <name> -n <ns>

    Show the whole chain: Certificate, Request, Order, Challenge and the exact ACME error

  • cmctl inspect secret <name> -n <ns>

    Decode tls.crt and show the issuer, SANs and validity dates without piping into openssl x509

  • kubectl apply -f - <<EOF apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: letsencrypt-dns spec: acme: server: https://acme-v02.api.letsencrypt.org/directory privateKeySecretRef: name: letsencrypt-dns solvers: - dns01: route53: region: us-east-1 hostedZoneID: <id> EOF

    DNS01 issuer for wildcard certificates; IRSA or a secret must allow changing Route53 records

all 16 cert-manager commands