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

Contour

Active
Server Software Latest Version: 1.33.1 Latest Release: Dec 22, 2025

Contour is a Kubernetes ingress controller using Envoy proxy for HTTP/HTTPS routing.

Versions

10

Latest Version

1.33.1

Active Support

3

EOL

7

Lifecycle Timeline

Today
1.33
1.33
1.32
1.32
1.31
1.31
1.30
1.30
1.29
1.29
1.28
1.28
1.27
1.27
1.26
1.26
1.25
1.25
1.24
1.24
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.33Sep 8, 2025-No1.33.1No
Active
1.32May 15, 2025-No1.32.2No
Active
1.31May 6, 2025-No1.31.3No
Active
1.30Jul 31, 2024-Sep 8, 20251.30.5No
EOL
1.29May 7, 2024-May 15, 20251.29.5No
EOL
1.28Feb 12, 2024-May 6, 20251.28.8No
EOL
1.27Oct 30, 2023-Jul 31, 20241.27.4No
EOL
1.26Aug 29, 2023-May 7, 20241.26.3No
EOL
1.25May 9, 2023-Feb 12, 20241.25.3No
EOL
1.24Jan 31, 2023-Oct 30, 20231.24.6No
EOL

Frequently Asked Questions

Which versions of Contour have reached end of life?
The following Contour versions have reached end of life and no longer receive security updates: 1.30, 1.29, 1.28, 1.27, 1.26, 1.25, 1.24. It is recommended to upgrade to a supported version.
Is it safe to continue using Contour 1.30?
Contour 1.30 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 Contour?
The latest version of Contour is 1.33.1, released in the 1.33 release cycle.
How many versions of Contour are currently supported?
Contour currently has 3 actively supported version(s): 1.33, 1.32, 1.31.
When does Contour 1.33 reach end of life?
Contour 1.33 does not have a specific end-of-life date announced yet.
What should I do when Contour reaches end of life?
When a Contour 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.