External Secrets Operator End of Life (EOL) Dates & Support Timeline

External Secrets Operator lifecycle status — the real story

External Secrets Operator syncs secrets from external stores (AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, Google Secret Manager and others) into Kubernetes. The project supports only the most up-to-date minor version: an older minor is deprecated as soon as a new minor ships, and new minors arrive every few weeks. The project's Stability and Support table prints a release day and an end of life day for every minor except the current one, whose end is the release of the next minor. Release and patch dates come from the project's GitHub releases, which differ from the table for a few old lines.

External Secrets Operator release and support pattern

Across the 36 release lines with a published release date, External Secrets Operator has shipped a new line roughly every 4 weeks (median interval). A line typically stays supported for about 4 weeks from its release to its end-of-life date (measured on the 35 lines with both dates published).

Of the 36 release lines tracked, 35 are past end of life and 1 is still within support. The newest line, 2.13, was released October 16, 2026. No end-of-life date is currently published for the 1 supported line.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does External Secrets Operator end of life mean for your organization?

When a version of External Secrets Operator reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL External Secrets Operator should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when External Secrets Operator reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL External Secrets Operator versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products