Tetrate Service BridgeVersion: 1.14.xSupport Policy
TSB Releases explained
We develop and release Tetrate Service Bridge on an incremental basis, using an Agile-like approach to deliver feature updates and fixes to customers promptly.
Prior to 1.14.4000, the TSB version numbering followed a X.Y.Z scheme, where releases were made every 6-8 weeks and CVE fixes were included in the following release. A release would be issued on an exceptional basis for critical, exploitable vulnerabilities.
From 1.14.4000 and beyond, TSB releases will include more frequent CVE patch releases. In each patch release, the final digits will be incremented. For example, 1.14.4007 denotes the 7th CVE patch release of the 1.14.4000 feature release.
Our versioning uses a MAJOR.MINOR.POINT PATCH version numbering style (e.g. 1.14.4000):
- We make point releases typically every 8-10 weeks. These releases include new features.
- For each point feature release, we make further CVE patch releases, e.g.
1.14.4007.
In addition:
- We make minor releases typically every 6 months (2 per year), aligning with Istio releases.
- The major version number is unchanged from our first generally-available release
Point feature releases and CVE Patch releases
Point releases (e.g. 1.14.4000) contain are the means to ship bug fixes and new TSB features. They include:
- Incremental additions to existing features
- New or extended APIs (breaking changes are avoided as far as possible)
- New features, disabled-by-default with feature flags where judged necessary
For the current Point release, we make subsequent CVE Patch releases, where the final digits of the release number are incremented. CVE Patch releases only contain necessary fixes for CVEs.
We test upgrade paths from a variety of earlier releases extensively, but please contact Tetrate support if you want advice and confirmation before commencing a significantly-large upgrade.
Minor Releases
In addition, a minor release may contain:
- Significant changes to dependencies such as Istio
- Significant breaking changes (these are to be avoided as far as possible)
When we make a minor release, we will also:
- Update the documentation, creating a new
latestversion and leaving the previous version available for reference - Assess our feature maturity, announcing features that are promoted to 'Generally-Available' status, or features that will be retired in later releases
CVE Patch releases for older Releases
Tetrate will, at our discretion, maintain CVE Patch releases for chosen older releases.
Support Policy
All versions of the current minor release (e.g. 1.14.x are fully supported). CVE Patches are available for the most recent POINT release in that MINOR release.
When a new MINOR release (e.g. 1.15.000) is made available, previous MINOR releases fall under the long term support 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).
End of General Support (EoGS) for a MINOR release (e.g. 1.12.x) is the later of:
- 12 months after the release of the first
Minorrelease e.g. 1.12.0 - The date of the N+3
MINORrelease, e.g. 1.15.0
... meaning that generally, TSB MINOR versions N, N-1 and N-2 are fully supported (our N-2 support policy), and each minor version is supported for a minimum of 1 year after initial release.
We strongly recommend that at a minimum, you upgrade to the current MINOR release at least once a year in order to remain in support and to have access to security and product fixes.
Our recommended best practice is to follow our most recent release, and to monitor the CVE Patch release stream in order to remain current and compliant with security best practice. We use feature flags to disable significant new features, in order to reduce any perceived risk of running the most recent feature releases.
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 selected MINOR version, through the use of POINT or CVE Patch releases. A new release does not reset the support lifetime duration, as it is tied to the initial MINOR release.
TSB EoGS dates
EoGS dates may be extended according to the policy explained above.
| TSB Version | General Availability | End of General Support |
|---|---|---|
| TSB v1.14.x | 1 April, 2026. | On release of 1.17.0 |
| TSB v1.13.x (*) | 4 September, 2025 | 1 April, 2026 |
| TSB v1.12.x | 27 February, 2025 | On release of 1.15.0 |
| TSB v1.11.x | 15 November, 2024 | 30 August, 2026 |
| TSB v1.10.x | 17 July, 2024 | 4 September, 2025 |
| TSB v1.9.x | 12 April, 2024 | 11 April, 2025 |
| TSB v1.8.x | 21 December, 2023 | 20 December, 2024 |
| TSB v1.7.x | 15 September, 2023 | 31 May, 2024 |
| TSB v1.6.x | 1 January, 2023 | 1 March, 2024 |
| TSB v1.5.x | 15 July, 2022 | 22 December, 2023 |
| TSB v1.4.x | 1 November, 2021 | 31 October, 2022 |
| TSB v1.3.x | 1 June, 2021 | 31 May, 2022 |
| TSB v1.2.x | 1 May, 2021 | 30 April, 2022 |
| TSB v1.1.x | 1 April, 2021 | 31 March, 2022 |
| TSB v1.0.x | 1 March, 2021 | 28 February, 2022 |
(*) For operational efficiencies, TSB 1.13.x is no longer maintained. Updates and CVE fixes will not be issued.
TSB Platform compatibility
Tetrate maintains the commitment to test TSB compatibility with Generally Supported k8s versions (approximately most recent three minor releases). For details on Kubernetes release policy refer to this document.
Tetrate maintains the commitment to test TSB Compatibility with OpenShift releases that are either in Full Support or Maintenance Support phase of their lifecycle. Generally, this means most recent 4 minor OpenShift releases. For details on OpenShift Life Cycle Policy refer to official RedHat documentation.
Where possible, Tetrate makes its best effort to verify TSB compatibility with earlier platform releases that may have reached their EoL. For further details, please refer to Tetrate support.
Additionally, Tetrate makes its best effort to verify TSB compatibility with MKE 3.7+
| TSB Release | Verified Kubernetes Versions | Verified OpenShift Versions |
|---|---|---|
| TSB v1.14.4000 | 1.34-1.36 | 4.19-4.21 |
| TSB v1.14.3 | 1.33-1.35 | 4.18-4.21 |
| TSB v1.14.2 | 1.33-1.35 | 4.18-4.21 |
| TSB v1.14.1 | 1.33-1.35 | 4.18-4.21 |
| TSB v1.14.0 | 1.33-1.35 | 4.18-4.21 |
TSB Supported Additional Platforms
Tetrate Service Bridge supports additional platforms for workload onboarding onto the mesh:
| Platforms | Notes |
|---|---|
| AWS EC2 - virtual machine instances | Onboarding authenticated using AWS Account credentials |
| AWS ECS tasks | See notes |
| On-prem or other cloud-hosted VMs | Onboarding authenticated using JWT tokens |
Onboarding is handled by a Tetrate Onboarding Agent and Istio Sidecar. Tetrate provide packages for the following environments:
| Supported OS | Notes |
|---|---|
| RHEL family | RHEL 8+, Amazon Linux 2023; installation via RPM packages |
| Debian family | Debian 9+, Ubuntu 20.04+; installation via DEB packages |
TSB Component Version Matrix
Tetrate Service Bridge comes with the following open source components
| TSB | Istio | Envoy | SkyWalking | Cert Manager | OpenTelemetry Collector |
|---|---|---|---|---|---|
| 1.14.3005 | 1.28.9 | 1.36.10 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v28 | 0.159.0 |
| 1.14.3004 | 1.28.9 | 1.36.10 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v28 | 0.159.0 |
| 1.14.3003 | 1.28.9 | 1.36.9 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v28 | 0.159.0 |
| 1.14.3002 | 1.28.9 | 1.36.9 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v27 | 0.159.0 |
| 1.14.3001 | 1.28.9 | 1.36.9 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v23 | 0.154.0 |
| 1.14.3000 | 1.28.9 | 1.36.9 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v23 | 0.154.0 |
| 1.14.3 | 1.28.9 | 1.36.9 | 10.4.0-20260702-023055 | v1.16.1-tetrate-v23 | 0.154.0 |
| 1.14.2 | 1.28.3 | 1.36.7 | 10.4.0-20260312-023839 | v1.16.1-tetrate-v19 | 0.152.0 |
| 1.14.1 | 1.28.3 | 1.36.5 | 10.4.0-20260312-023839 | v1.16.1-tetrate-v19 | 0.152.0 |
| 1.14.0 | 1.28.3 | 1.36.5 | 10.4.0-20260312-023839 | v1.16.1-tetrate-v14 | 0.148.0 |
TSB Feature Definitions Terminology
Features in TSB are designated in 5 different stages as described below. Any stages apart from the Production (Default) stage, are identified in the Feature Status Table, API References, and Guides.
| Feature Stage | Notes |
|---|---|
| Alpha | Disabled by default, and can be enabled only by Tetrate Support. These features are for customers' initial testing, and for collecting feedback |
| Beta | Limited availability feature that is pre-Production standard. These features are for customers' evaluation within any licensing or feature flag restrictions. The API is subject to change, although unlikely |
| Production | Default - These features are Generally Available for use in Production. Any feature that has not been explicitly identified in any of the other stages can be considered as Production-ready |
| Deprecated | These features are deprecated from the Product and will be removed in a future release based on the their impact and usage (see the Deprecation Policy below for details) |
| End of Life | These features are End of Life and will be removed from the Product |
TSB Deprecation Policy
- Features that are deprecated are identified in the Release Notes, API references, and Guides.
- The information also includes the Release in which they are deprecated and the Release in which they will be removed (End of Life).
- When a feature is deprecated, users should stop using the feature, or migrate to any recommended alternate solutions.
- Upon deprecation, the feature is removed (End of Life) from the product 2 or 4 minor releases later as annotated per-feature in the Feature Status Table.
Please work with your Customer Engineering Representative or Tetrate Support to plan the migration from the feature(s) that are deprecated to the recommended alternate solutions.