
Cert Manager
- 12 installs
- 1 repo stars
- Updated March 10, 2026
- davidcastagnetoa/skills
Use cert-manager in Kubernetes to automatically issue and renew TLS certificates from Let's Encrypt via ClusterIssuer and Ingress annotations.
About
Automates the TLS certificate lifecycle in Kubernetes, issuing and renewing Let's Encrypt certs through a ClusterIssuer and Ingress annotations. A developer uses it to keep certificates from expiring on externally and internally exposed services.
- ClusterIssuer with ACME http01 solver for Let's Encrypt
- Auto-renewal 30 days before expiry with staging for rate limits
Cert Manager by the numbers
- 12 all-time installs (skills.sh)
- Ranked #978 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidcastagnetoa/skills --skill cert_managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 12 |
|---|---|
| repo stars | ★ 1 |
| Last updated | March 10, 2026 |
| Repository | davidcastagnetoa/skills ↗ |
What it does
Use cert-manager in Kubernetes to automatically issue and renew TLS certificates from Let's Encrypt via ClusterIssuer and Ingress annotations.
Files
cert_manager
cert-manager automatiza el ciclo de vida de los certificados TLS: solicitud, validación, emisión y renovación. Integrado con Let's Encrypt, garantiza que los certificados nunca expiran y elimina el trabajo manual de gestión de TLS.
When to use
Usar en el cluster Kubernetes de producción para todos los servicios expuestos externamente (Nginx Ingress) e internamente (comunicaciones entre microservicios si no se usa Istio).
Instructions
1. Instalar cert-manager en Kubernetes:
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.13.0/cert-manager.yaml2. Crear ClusterIssuer para Let's Encrypt:
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt-prod
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
email: security@company.com
privateKeySecretRef:
name: letsencrypt-prod-key
solvers:
- http01:
ingress:
class: nginx3. Añadir anotación en el Ingress de Nginx:
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
tls:
- hosts: [api.kyc.company.com]
secretName: kyc-api-tls4. cert-manager renueva automáticamente 30 días antes de expiración. 5. Verificar estado: kubectl get certificates -A y kubectl describe certificate kyc-api-tls. 6. Para comunicaciones internas mTLS sin Istio, usar ClusterIssuer con CA propia (SelfSigned o Vault PKI).
Notes
- Let's Encrypt tiene rate limits — en staging usar
letsencrypt-stagingpara pruebas. - Para dominios internos (
.svc.cluster.local), usar una CA interna gestionada por Vault PKI Engine. - Alertar con Prometheus si algún certificado expira en menos de 14 días (fallo del proceso de renovación).
List_Agents.md
list_skills.md
CLAUDE.md
Agents.md
.DS_Store