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

Gatekeeper

Active
Server Software Latest Version: 3.21.1 Latest Release: Feb 4, 2026

OPA Gatekeeper is a policy controller for Kubernetes that enforces policies using Open Policy Agent.

Versions

11

Latest Version

3.21.1

Active Support

2

EOL

9

Lifecycle Timeline

Today
3.21
3.21
3.20
3.20
3.19
3.19
3.18
3.18
3.17
3.17
3.16
3.16
3.15
3.15
3.14
3.14
3.13
3.13
3.12
3.12
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.21Nov 19, 2025-No3.21.1No
Active
3.20Jul 24, 2025-No3.20.1No
Active
3.19Apr 9, 2025-Nov 19, 20253.19.3No
EOL
3.18Dec 12, 2024-Jul 24, 20253.18.3No
EOL
3.17Aug 21, 2024-Apr 9, 20253.17.2No
EOL
3.16May 9, 2024-Dec 12, 20243.16.3No
EOL
3.15Feb 5, 2024-Aug 21, 20243.15.1No
EOL
3.14Nov 1, 2023-May 9, 20243.14.2No
EOL
3.13Aug 8, 2023-Feb 5, 20243.13.4No
EOL
3.12Apr 14, 2023-Nov 1, 20233.12.0No
EOL
3.11Jan 4, 2023-Aug 8, 20233.11.1No
EOL

Frequently Asked Questions

Which versions of Gatekeeper have reached end of life?
The following Gatekeeper versions have reached end of life and no longer receive security updates: 3.19, 3.18, 3.17, 3.16, 3.15, 3.14, 3.13, 3.12 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Gatekeeper 3.19?
Gatekeeper 3.19 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 Gatekeeper?
The latest version of Gatekeeper is 3.21.1, released in the 3.21 release cycle.
How many versions of Gatekeeper are currently supported?
Gatekeeper currently has 2 actively supported version(s): 3.21, 3.20.
When does Gatekeeper 3.21 reach end of life?
Gatekeeper 3.21 does not have a specific end-of-life date announced yet.
What should I do when Gatekeeper reaches end of life?
When a Gatekeeper 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.