Skip to main content
logoTetrate Service BridgeVersion: next

TSB Support Policy

TSB Releases explained

TSB follows a semantic versioning model based on https://semver.org. This means we use a MAJOR.MINOR.PATCH version numbering style (e.g. v1.4.0).

This model describes that:

  1. MAJOR version is incremented when incompatible API changes are made.
  2. MINOR version is incremented when new features are added.
  3. PATCH version is incremented when bug and security fixes are handled.

TSB Release Cadence and Support

Tetrate releases 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 each eligible MINOR version, through the use of PATCH releases (e.g. 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 Candidates

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.

Supported Upgrade Policy

TSB employs a structured upgrade policy to ensure compatibility and stability across its platform versions. This policy is defined as N-1, which indicates that any given version of TSB Management Plane (MP) is guaranteed to work seamlessly with the Control Plane (CP) version immediately preceding it.

Understanding the N-1 Upgrade Policy

  • For any TSB Management Plane version, denoted as 1.x, compatibility is assured with the 1.(x-1) version of the TSB Control Plane.
  • For instance, if you are using TSB Management Plane (MP) version 1.8.x, it is guaranteed to be compatible with TSB Control Plane (CP) version 1.7.x.
  • However, this policy does not guarantee compatibility with Control Plane versions that are two or more releases behind the current Management Plane version. Continuing the previous example, TSB MP 1.8.x would not be guaranteed to work with CP 1.6.x.

Implications for Upgrading

  • When planning upgrades, it is important to consider this policy to ensure compatibility between the Management Plane and Control Plane versions.
  • This policy aids in maintaining a stable and predictable environment, reducing the risks associated with version incompatibility.

Recommendations

  • Users are advised to regularly update their Control Plane versions to stay within the N-1 compatibility range of their Management Plane version.
  • Staying up-to-date with the latest releases not only ensures compatibility but also provides access to the latest features and security updates.

Supported Versions

In LTS support lifetime, Tetrate will supply patches, security fixes for its components, and the underlying OSS dependencies as described in our component matrix.

Features are not back ported, please see the release notes and the feature status documents for released features.

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 VersionGeneral AvailabilityEnd of General SupportKubernetes VersionsOpenShift Versions
TSB v1.9.x12 April, 202411 April, 20251.26 - 1.294.12 - 4.14
TSB v1.8.x21 December, 202320 December, 20241.25 - 1.294.12 - 4.14
TSB v1.7.x15 September, 202331 May, 20241.24 - 1.294.10 - 4.14
TSB v1.6.x1 January, 20231 March, 20241.22 - 1.28 [1]4.7 - 4.13 [1]
TSB v1.5.x15 July, 202222 December, 20231.19 - 1.244.6 - 4.11
TSB v1.4.x1 November, 202131 October, 20221.18 - 1.21 [2]4.6 - 4.8
TSB v1.3.x1 June, 202131 May, 20221.18 - 1.204.6 - 4.8
TSB v1.2.x1 May, 202130 April, 20221.18 - 1.20 [3]4.6 - 4.8
TSB v1.1.x1 April, 202131 March, 2022
TSB v1.0.x1 March, 202128 February, 2022

Notes

  • [1] Kubernetes 1.27.7, 1.28.3 and OpenShift 4.12.44, 4.13.23 require TSB 1.6.7 or later, TSB 1.6.5 also supports 4.14.9
  • [2] Kubernetes 1.21 and TSB 1.4.x - supported with caveats, please refer to Tetrate support
  • [3] 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

TSBIstioEnvoySkyWalkingZipkinOpenTelemetry Collector
master1.20.31.28.110.0.0-20231208-14090.91.0