Commit activity
Last 12 weeks · 0 commits
Community health
3 of 6 standards met
57
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 6 discussions · Last activity 8y ago
See all on GitHub →
Let's Encrypt certs expire every 6 months right? Does kube-cert-manager handle renewals? P.S. Thank you for this project!
Kubernetes is moving away from Third Party Resources and on to Custom Resources instead: https://kubernetes.io/docs/tasks/access-kubernetes-api/migrate-third-party-resource/ Is there a straight forward way to migrate the kube-cert-manager Certificates over to a Custom Resource Definition instead?
Create the Certificate Third Party Resource: kubectl create -f extensions/certificate.yaml Where is this yaml file?
Recent fixes
Given that many forks of exists I wish to simplify this project and reduce it's scope to a single DNS provider and remove the support for watching events. Going forward the only DNS provider I plan to support is Google Cloud DNS and drop support for DNS exec plugins. Given that a sync loop is required to ensure all certificates get processed in a timely manner I'm planning to drop watch support. This will impact the responsiveness of the system. When certificate objects are created it will take up to 30 seconds before they are processed. People who want more features will be directed to one of the popular forks in the README.
Structured data for AI agents
Repository: kelseyhightower/kube-cert-manager. Description: Manage Lets Encrypt certificates for a Kubernetes cluster. Stars: 1108, Forks: 136. Primary language: Go. Languages: Go (100%). License: Apache-2.0. Open PRs: 0, open issues: 6. Last activity: 8y ago. Community health: 57%. Top contributors: kelseyhightower, beeradb, sfrique, broady, apstndb, jmhodges, kasperbe, ismailbaskin.