Skip to content
Skills Library
DevOps & cloud · Automation

cert-manager

/cert-manager

cert-manager issues and renews TLS certificates automatically inside Kubernetes, from Let's Encrypt (ACME) or a private CA. Use when someone asks to "get HTTPS on my Kubernetes ingress", "set up Let's Encrypt in a cluster", "create a ClusterIssuer", "issue a wildcard certificate", "renew a certificate" or "debug a certificate stuck in pending".

Repository
skills ↗
Licence
Apache-2.0
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
6
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

cert-manager issues and renews TLS certificates automatically inside Kubernetes, from Let's Encrypt (ACME) or a private CA. Use when someone asks to "get HTTPS on my Kubernetes ingress", "set up Let's Encrypt in a cluster", "create a ClusterIssuer", "issue a wildcard certificate", "renew a certificate" or "debug a certificate stuck in pending".

Triggers from the description

s Encrypt (ACME) or a private CA. Use when someone asks toset up Letcreate a ClusterIssuerissue a wildcard certificaterenew a certificatedebug a certificate stuck in pending
Original author description

cert-manager issues and renews TLS certificates automatically inside Kubernetes, from Let's Encrypt (ACME) or a private CA. Use when someone asks to "get HTTPS on my Kubernetes ingress", "set up Let's Encrypt in a cluster", "create a ClusterIssuer", "issue a wildcard certificate", "renew a certificate" or "debug a certificate stuck in pending".

How it works

  1. Overview
  2. Instructions
  3. Examples
  4. Guidelines
Original SKILL.md headings · 218 lines, 1,072 words
SKILL.md preview
---
name: cert-manager
description: >-
  cert-manager issues and renews TLS certificates automatically inside
  Kubernetes, from Let's Encrypt (ACME) or a private CA. Use when someone asks
  to "get HTTPS on my Kubernetes ingress", "set up Let's Encrypt in a
  cluster", "create a ClusterIssuer", "issue a wildcard certificate", "renew a
  certificate" or "debug a certificate stuck in pending".
license: Apache-2.0
compatibility: "Kubernetes (a release supported by cert-manager 1.21), Helm 3+, kubectl; cmctl optional"
metadata:
  author: terminal-skills
  version: "1.1.0"
  category: devops
  tags: "cert-manager, tls, kubernetes, letsencrypt, certificates"
  repository: https://github.com/cert-manager/cert-manager
---

# cert-manager

## Overview

cert-manager adds `Issuer`, `ClusterIssuer` and `Certificate` resources to Kubernetes. A `Certificate` asks an issuer for a key pair, stores it in a `Secret`, and renews it before it expires. Issuers can be ACME (Let's Encrypt, ZeroSSL), a private CA stored in a Secret, self-signed, Vault and others. The current release is v1.21.3. Let's Encrypt validation is either HTTP-01 (an `/.well-known/acme-challenge` path served through your ingress) or DNS-01 (a TXT record; required for wildcards).

## Instructions

### 1. Install

The project recommends the OCI chart (the Jetstack HTTP repository is updated a few hours after each release):

```bash
helm install cert-manager oci://quay.io/jetstack/charts/cert-manager \
  --version v1.21.3 \
  --namespace cert-manager \
  --create-namespace \
  --set crds.enabled=true
kubectl get pods -n cert-manager
```

With the legacy repository: `helm repo add jetstack https://charts.jetstack.io --force-update` and `jetstack/cert-manager`. `crds.enabled=true` installs the CRDs with the chart (the old `installCRDs` value is replaced by it). Never install cert-manager as a subchart. Verify the API with `cmctl check api` (`brew install cmctl` or the release binary from GitHub).

### 2. ClusterIssuers for Let's Encrypt

Start with staging (untrusted certificates, generous rate limits), then switch to production:

```yaml
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    email: platform@northwind-shop.io
    privateKeySecretRef:
      name: letsencrypt-staging-account-key
    solvers:
      - http01:
          ingress:
            ingressClassName: nginx
---
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email: platform@northwind-shop.io
    privateKeySecretRef:
      name: letsencrypt-prod-account-key
    solvers:
      - http01:
          ingress:
            ingressClassName: nginx
```

Use `ingressClassName`; the older `class` field is the legacy form. The email receives account notices. Optional `profile: tlsserver` (cert-manager 1.18+) asks Let's Encrypt for its 45-day, no-Common-Name certificates; unset means the `classic` 90-day profile. A profile name the server does not know produces an error on the Order, so check the directory (`curl -fsSL https://acme-v02.api.letsencrypt.org/directory`) first.

### 3. DNS-01 (wildcards, private clusters)

Wildcards need DNS-01. Solvers are matched by `selector`, so one issuer can use HTTP-01 for most names and DNS-01 for one zone:

```yaml
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-dns
spec:
  acme:
    server: https://acme-v02.api.letsencrypt.org/directory
    email: platform@northwind-shop.io
    privateKeySecretRef:
      name: letsencrypt-dns-account-key
    solvers:
      - selector:
          dnsZones:
            - northwind-shop.io
        dns01:
          route53:
            region: eu-west-1
            hostedZoneID: Z0412345ABCDEFGHIJKLM
```

With Route 53 leave out access keys when cert-manager runs with EKS Pod Identity or IRSA (ambient credentials, used by `ClusterIssuer` only by default); otherwise reference a Secret with `accessKeyIDSecretRef` and `secretAccessKeySecretRef`. Other providers use `cloudDNS`, `cloudflare`, `azureDNS`, or a webhook solver. Give the DNS identity access to that zone only.

### 4. Certificates

```yaml
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: wildcard-northwind-shop
  namespace: default
spec:
  secretName: wildcard-northwind-shop-tls
  issuerRef:
    name: letsencrypt-dns
    kind: ClusterIssuer
  dnsNames:
    - northwind-shop.io
    - "*.northwind-shop.io"
  duration: 2160h      # 90 days requested; Let's Encrypt decides the real lifetime
  renewBefore: 720h    # start renewing 30 days before expiry
  privateKey:
    algorithm: ECDSA
    size: 256
    rotationPolicy: Always   # the default, shown for clarity
```

List names in `dnsNames`; avoid `commonName` on leaf certificates (the docs advise against it). Durations use Go syntax (`h`, `m`, `s`, no days). Let's Encrypt ignores `duration` and issues what its profile defines (90 days for `classic`, 45 for `tlsserver`), and `renewBefore` must be shorter than that lifetime.

### 5. Internal CA

```yaml
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: selfsigned-bootstrap
spec:
  selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: internal-ca
  namespace: cert-manager
spec:
  isCA: true
  commonName: northwind-internal-ca
  secretName: internal-ca-secret
  issuerRef:
    name: selfsigned-bootstrap
    kind: ClusterIssuer
  privateKey:
    algorithm: ECDSA
    size: 256
---
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: internal-ca-issuer
spec:
  ca:
    secretName: internal-ca-secret
```

A `ClusterIssuer` reads the CA Secret from cert-manager's own namespace (`cert-manager`), which is why the CA Certificate lives there.

### 6. Ingress and Gateway integration

Annotate an Ingress and cert-manager's ingress-shim creates the Certificate for each `tls` entry:

```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-app
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - app.northwind-shop.io
        - api.northwind-shop.io
      secretName: app-northwind-shop-tls
  rules:
    - host: app.northwind-shop.io
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: web-app
                port:
                  number: 80
```

For Gateway API, install the Gateway API CRDs first, then enable it in the chart: `--set config.gatewayAPI.enabled=true` (restart the cert-manager Deployment if the CRDs arrived after it). Annotate the `Gateway` with the same `cert-manager.io/cluster-issuer` annotation and give each HTTPS listener `tls.certificateRefs`. For Istio's ingress gateway, create a `Certificate` in `istio-system` and reference its Secret from the Gateway.

### 7. Inspect and debug

```bash
kubectl get certificate -A
cmctl status certificate wildcard-northwind-shop -n default
cmctl renew wildcard-northwind-shop -n default
kubectl get certificaterequest,order,challenge -A
kubectl describe challenge -n default
kubectl logs -n cert-manager deploy/cert-manager --tail=100
kubectl get secret wildcard-northwind-shop-tls -o jsonpath='{.data.tls\.crt}' | base64 -d | openssl x509 -noout -subject -dates -ext subjectAltName
```

## Examples

### Example 1: "Put HTTPS on app.northwind-shop.io"

Install (step 1), apply `letsencrypt-staging`, annotate the Ingress with `cert-manager.io/cluster-issuer: letsencrypt-staging`, and watch `kubectl get certificate -w` until `READY` is `True` (usually under two minutes). Then change the annotation to `letsencrypt-prod` and delete the old Secret so a trusted certificate is requested.

### Example 2: "A certificate has been Pending for 20 minutes"

`cmctl status certificate <name>` shows the stage. Follow the chain with `kubectl get order,challenge -A`; `kubectl describe challenge` states why. Typical causes: DNS for the host does not point at the ingress (HTTP-01), the ingress class name does not match the solver, a `www`-redirect or auth rule blocks `/.well-known/acme-challenge/`, DNS-01 credentials lack permission on the zone, or Let's Encrypt rate limits were hit (switch to staging while testing).

## Guidelines

- Test with the staging issuer first; production has rate limits (for example, a limited number of certificates per registered domain per week) and failed validations count.
- Never delete the account-key Secret of a production issuer casually; you lose the ability to revoke certificates issued under that account.
- Back up internal CA Secrets; losing `internal-ca-secret` means reissuing everything that chains to it.
- Wildcards need DNS-01. HTTP-01 cannot validate `*.` names and needs port 80 reachable from the internet.
- Pods only see a new certificate when they reload it; mount the Secret as a volume (not an env var) and use a reloader or an app that watches the file. Ingress controllers pick it up themselves.
- `rotationPolicy` defaults to `Always` (a new private key on every renewal); set `Never` only if something pins the key.
- Restrict who can create `Certificate` and `Issuer` objects; any user able to reference a `ClusterIssuer` can request certificates for hostnames it can solve.
- cert-manager supports only recent Kubernetes versions; check the supported-releases page before upgrading, and upgrade one minor version at a time.
Files in this package (2)
  • SKILL.md 9 KB
  • _scores.json 1 KB

Versions

The database has no other skills named cert-manager.

Database snapshot: 13.11.2026 · package version 1cc192e4f77e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cert-manager-tls-automation
    Guides installing and configuring cert-manager for automated TLS certificate issuance and renewal — Issuers vs. ClusterIssuers, ACME/ Let's Encrypt HTTP-01 and DNS-01 challenges, private-CA issuance, and integration with Ingress-nginx and Istio gateways. Use when a user asks to…
  • 100k8s-cert-manager-troubleshooting
    Use when cert-manager does not issue or renew a certificate in Kubernetes: a Certificate that stays READY False, a CertificateRequest that is Pending, Denied or Failed, an Issuer or ClusterIssuer that is not Ready ("Error getting keypair for CA issuer"), "Referenced \"Issuer\"…
  • 90certificate-monitoring
    Use when the user asks about SSL/TLS certificates, certificate expiration, monitoring domains for cert health, or issuing free Let's Encrypt certificates. Triggers include "is my cert expiring", "scan ssl on X", "check certificate", "monitor this domain", "issue a free cert",…
  • 100certificate-management
    Use when managing TLS certificates and PKI infrastructure — issuing, renewing, or rotating certificates, debugging TLS handshake failures, managing cert-manager in Kubernetes, operating an internal CA, creating CSRs, or checking certificate expiration. Also use for "certificate…
  • 100letsencrypt
    Let's Encrypt is a free, automated certificate authority, and Certbot is its official ACME client for getting and renewing TLS certificates. Use this skill when asked to add HTTPS to a website, get a free SSL certificate, issue a wildcard certificate, set up automatic renewal,…
  • 100certbot
    Expert Certbot SSL/TLS certificate assistance covering Let's Encrypt, ACME DNS/HTTP validation, and auto-renewal. Use when provisioning SSL certificates, setting up HTTPS, or troubleshooting cert renewals.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.