EOL.Wiki EOL.Wiki
← ← Back to all products

cert-manager

Active
DevOps & CI/CD Latest Version: 1.19.3 Latest Release: Feb 2, 2026

cert-manager is a Kubernetes add-on for automating the management and issuance of TLS certificates.

Versions

10

Latest Version

1.19.3

Active Support

2

EOL

8

Lifecycle Timeline

Today
1.19
1.19
1.18
1.18
1.17
1.17
1.16
1.16
1.15
1.15
1.14
1.14
1.13
1.13
1.12
1.12
1.11
1.11
1.10
1.10
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.19Oct 7, 2025-No1.19.3No
Active
1.18Jun 10, 2025-No1.18.5No
Active
1.17Feb 3, 2025-Oct 7, 20251.17.4No
EOL
1.16Oct 3, 2024-Jun 10, 20251.16.5No
EOL
1.15Jun 5, 2024-Feb 3, 20251.15.5No
EOL
1.14Jan 31, 2024-Oct 3, 20241.14.7No
EOL
1.13Sep 12, 2023-Jun 5, 20241.13.6No
EOL
1.12May 19, 2023-May 19, 20251.12.17
Yes
EOL
1.11Jan 11, 2023-Sep 12, 20231.11.5No
EOL
1.10Oct 17, 2022-May 19, 20231.10.2No
EOL

Frequently Asked Questions

Which versions of cert-manager have reached end of life?
The following cert-manager versions have reached end of life and no longer receive security updates: 1.17, 1.16, 1.15, 1.14, 1.13, 1.12, 1.11, 1.10. It is recommended to upgrade to a supported version.
Is it safe to continue using cert-manager 1.17?
cert-manager 1.17 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of cert-manager?
The latest version of cert-manager is 1.19.3, released in the 1.19 release cycle.
How many versions of cert-manager are currently supported?
cert-manager currently has 2 actively supported version(s): 1.19, 1.18.
When does cert-manager 1.19 reach end of life?
cert-manager 1.19 does not have a specific end-of-life date announced yet.
What should I do when cert-manager reaches end of life?
When a cert-manager version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.