TSB Releases explained
TSB follows a semantic versioning model based on https://semver.org. This means
we use a
PATCH version numbering style (e.g.
This model describes that:
MAJORversion is incremented when incompatible API changes are made.
MINORversion is incremented when new features are added.
PATCHversion is incremented when bug and security fixes are handled.
TSB Release Cadence and Support
PATCH updates (
1.x.y) to supported TSB versions on a regular
basis, and at least quarterly.
Each release of a new
MINOR falls under the Long Term Support (LTS) policy, in which Tetrate provides support starting from the official General Availability (GA) release date of the
MINOR release, to the End of General Support (EoGS) set to 12 months after GA or N-2 (two versions prior to the latest TSB version), whichever is longer. Any release after EOGS will not be supported unless extended support has been arranged with Tetrate prior to the EoGS date.
During the release's support window, bug and security fixes will be provided for
MINOR version, through the use of
v1.x.1). A new
PATCH release does not reset the support lifetime
duration, as it is tied to the initial
MINOR release. Patch releases include
fixes for TSB specific components, as well as patch fixes for its open source
components like Envoy, Istio, SkyWalking, and Zipkin.
TSB Release Candidate versions
Next to the LTS versions, Tetrate can make interim "release candidate" versions available. These interim versions provide early access to new features to try out and test.
Release candidate versions are not meant for production usage and even in non production we strongly encourage you to understand that there might be bugs that are either described in the preliminary release notes, or are not yet known. Also note that, new features might not be fully completed and documented yet.
If interested in testing a release candidate, do not hesitate to contact your Tetrate representative for the context around the specific release candidate. Customers testing release candidate versions are strongly encouraged to upgrade to the next LTS version as soon as available.
In LTS support lifetime, Tetrate will supply patches, security fixes for its components, and the underlying OSS dependencies as described in our component matrix.
Each version (
1.x.y) of TSB supports the Kubernetes and OpenShift versions that were currently supported when the minor version was first released (
1.x.0). In addition, Tetrate makes best efforts to support earlier K8s and OpenShift versions for backwards-compatibility, and support later K8s and OpenShift versions in subsequent patch releases:
TSB EoGS dates based on planned upcoming releases
|TSB Version||General Availability||End of General Support||Kubernetes Versions||OpenShift Versions|
|TSB v1.6.x||1 January, 2023||1 March, 2024||1.22 - 1.26 ||4.7 - 4.12 |
|TSB v1.5.x||15 July, 2022||8 December, 2023||1.19 - 1.24||4.6 - 4.11|
|TSB v1.4.x||1 November, 2021||31 October, 2022||1.18 - 1.21 ||4.6 - 4.8|
|TSB v1.3.x||1 June, 2021||31 May, 2022||1.18 - 1.20||4.6 - 4.8|
|TSB v1.2.x||1 May, 2021||30 April, 2022||1.18 - 1.20 ||4.6 - 4.8|
|TSB v1.1.x||1 April, 2021||31 March, 2022|
|TSB v1.0.x||1 March, 2021||28 February, 2022|
-  Kubernetes 1.25, 1.26 and OpenShift 4.12 require TSB 1.6.1 or later
-  Kubernetes 1.21 and TSB 1.4.x - supported with caveats, please refer to Tetrate support
-  Kubernetes 1.19 and 1.20 and TSB 1.2.x - supported with caveats, please refer to Tetrate support
TSB Component Version Matrix
Tetrate Service Bridge comes with the following open source components