Although we try our best to maintain compatibility with the behavior of older versions during development, in some cases, breaking compatibility changes are unavoidable. We recommend deploying the same latest stable version on both the client and server sides.
Compatibility notes between different versions are as follows:
| Compatible Version Range | Description |
|---|---|
| >= 1.0.0, < 2.0.0 | These versions use Envoy as the data plane. |
| >= 2.0.0, <= 2.2.4 | Starting from 2.0.0, TNG transitioned to a data plane based on rustls and hyper. |
| 2.2.5 | Starting from this version, TNG uses OHTTP instead of the previous rats-tls over HTTP CONNECT protocol combination and introduces Passport model support. |
| >= 2.2.6 | Starting from this version, adjustments have been made to the OHTTP protocol to resolve design issues in HTTP routing scenarios encountered in version 2.2.5. |
| > 2.5.0 | Remote attestation now uses a pluggable provider layer. Wire formats for messages carrying evidence and attestation tokens are extended with optional provider fields in a backward-compatible way. Configuration parsing approach has changed significantly but relies on defaults to preserve compatibility with existing format. The as_is_grpc boolean configuration flag has been replaced by as_type: "grpc", existing configs using as_is_grpc must be updated. |