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

KubeEdge

Active
Cloud & Platforms Latest Version: 1.23.0 Latest Release: Mar 11, 2026

KubeEdge is a CNCF project that extends native Kubernetes orchestration to edge computing scenarios. Following Kubernetes-style policy, the three most recent minor releases are actively maintained.

Versions

8

Latest Version

1.23.0

Active Support

3

EOL

5

Lifecycle Timeline

Today
1.23
1.23
1.22
1.22
1.21
1.21
1.20
1.20
1.19
1.19
1.18
1.18
1.17
1.17
1.16
1.16
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.23Mar 11, 2026YesNo1.23.0No
Active
1.22Nov 5, 2025YesNo1.22.1No
Active
1.21Jun 18, 2025YesNo1.21.1No
Active
1.20Jan 21, 2025NoYes1.20.0No
EOL
1.19Oct 28, 2024NoYes1.19.2No
EOL
1.18Jul 25, 2024NoYes1.18.3No
EOL
1.17Apr 28, 2024NoYes1.17.5No
EOL
1.16Jan 23, 2024NoYes1.16.6No
EOL

Frequently Asked Questions

Which versions of KubeEdge have reached end of life?
The following KubeEdge versions have reached end of life and no longer receive security updates: 1.20, 1.19, 1.18, 1.17, 1.16. It is recommended to upgrade to a supported version.
Is it safe to continue using KubeEdge 1.20?
KubeEdge 1.20 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 KubeEdge?
The latest version of KubeEdge is 1.23.0, released in the 1.23 release cycle.
How many versions of KubeEdge are currently supported?
KubeEdge currently has 3 actively supported version(s): 1.23, 1.22, 1.21.
When does KubeEdge 1.23 reach end of life?
KubeEdge 1.23 does not have a specific end-of-life date announced yet.
What should I do when KubeEdge reaches end of life?
When a KubeEdge 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.