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

Kyverno

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

Kyverno is a policy engine designed for Kubernetes to validate, mutate, and generate configurations.

Versions

10

Latest Version

1.17.0

Active Support

4

EOL

6

Lifecycle Timeline

Today
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
1.9
1.9
1.8
1.8
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.17Feb 2, 2026-No1.17.0No
Active
1.16Nov 10, 2025-No1.16.3No
Active
1.15Jul 31, 2025-No1.15.3No
Active
1.14Apr 24, 2025-No1.14.5No
Active
1.13Oct 29, 2024-Nov 10, 20251.13.6No
EOL
1.12Apr 26, 2024-Jul 31, 20251.12.7No
EOL
1.11Nov 10, 2023-Apr 25, 20251.11.5No
EOL
1.10May 30, 2023-Oct 29, 20241.10.7No
EOL
1.9Feb 1, 2023-Apr 26, 20241.9.5No
EOL
1.8Oct 10, 2022-Nov 10, 20231.8.5No
EOL

Frequently Asked Questions

Which versions of Kyverno have reached end of life?
The following Kyverno versions have reached end of life and no longer receive security updates: 1.13, 1.12, 1.11, 1.10, 1.9, 1.8. It is recommended to upgrade to a supported version.
Is it safe to continue using Kyverno 1.13?
Kyverno 1.13 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 Kyverno?
The latest version of Kyverno is 1.17.0, released in the 1.17 release cycle.
How many versions of Kyverno are currently supported?
Kyverno currently has 4 actively supported version(s): 1.17, 1.16, 1.15, 1.14.
When does Kyverno 1.17 reach end of life?
Kyverno 1.17 does not have a specific end-of-life date announced yet.
What should I do when Kyverno reaches end of life?
When a Kyverno 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.