Versioning

Fury Kubernetes Distribution. Versioning policy

Stay updated with confidence.

Kubernetes Upstream Versions

The Kubernetes project maintains release branches for the most recent three minor releases. Also minor releases occur approximately every 3 months, so each minor release branch is maintained for approximately 9 months.

Kubernetes fury distribution aims to track three minor releases on each mayor of KFD version. that's at least 9 months of patches and updates analyzing its features.

Fury v1

The first stable release of the Kubernetes Fury Distribution supports:

  • Kubernetes 1.14
  • Kubernetes 1.15
  • Kubernetes 1.16

Meaning that you can install this distribution on top of any Kubernetes cluster 1.14.X, 1.15.X or 1.16.X as its core modules has been tested against these Kubernetes versions.

Every minor distribution release will include new features of its core modules. Patches works in the same way, KFD will release a patched version if any of its core module receives a patch.

Update procedure

All the mayor releases of KFD will include the upmost version of the previous mayor version, allowing you to update KFD in advance to update the upstream cluster version. so to recap. if using the Fury v1, ensure upstream kubernetes is on 1.16 (the upmost version), then update Fury to v2, and update kubernetes afterwards.



Last modified 08.04.2020: Change path (efaf729)