Support
Tetrate support is provided for the enterprise and enterprise FIPS editions of TEG under a TEG Subscription. The community edition carries no Tetrate support — see TEG Editions.
Join us in the #teg channel on the Tetrate Community Slack
TEG Versioning
TEG 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:
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.
TEG Supported Versions
The following versions of TEG are currently supported and will receive active bug fixes and security patches under a TEG Subscription:
| TEG Version | Release Date | End of Support |
|---|---|---|
| v0.1.0 | 21st September 2023 | 21st March 2024 |
| v1.0.x | 9th April 2024 | 9th November 2024 |
| v1.1.x | 6th August 2024 | 1st March 2025 |
| v1.2.x | 27th November 2024 | 1st November 2025 |
| v1.3.x | 5th February 2025 | 1st February 2026 |
| v1.4.x | 10th June 2025 | 1st June 2026 |
| v1.5.x | 22nd August 2025 | 1st August 2026 |
| v1.6.x | 8th December 2025 | 1st December 2026 |
| v1.7.x | 19th March 2026 | 1st March 2027 |
| v1.8.x | 19th May 2026 | 1st May 2027 |
| v1.9.x | 20th August 2026 | 1st August 2027 |
Kubernetes and Gateway API Support Matrix
TEG targets specific versions of Kubernetes and the Gateway API; below are the supported versions of Kubernetes and the Kubernetes Gateway API. Note that because the Gateway API is actively evolving, TEG requires relatively current versions of Kubernetes.
| TEG Version | Kubernetes Versions | Gateway API |
|---|---|---|
| v0.1.0 | v1.25, v1.26, v1.27 | v0.7.1 |
| v1.0.x | v1.26, v1.27, v1.28, v1.29 | v1.0.0 |
| v1.1.x | v1.27, v1.28, v1.29, v1.30 | v1.1.0 |
| v1.2.x | v1.28, v1.29, v1.30, v1.31 | v1.2.1 |
| v1.3.x | v1.29, v1.30, v1.31, v1.32 | v1.2.1 |
| v1.4.x | v1.30, v1.31, v1.32, v1.33 | v1.3.0 |
| v1.5.x | v1.30, v1.31, v1.32, v1.33 | v1.3.1 |
| v1.6.x | v1.30, v1.31, v1.32, v1.33 | v1.4.1 |
| v1.7.x | v1.32, v1.33, v1.34, v1.35 | v1.4.1 |
| v1.8.x | v1.32, v1.33, v1.34, v1.35 | v1.5.1 |
| v1.9.x | v1.33, v1.34, v1.35, v1.36 | v1.6.1 |
Component Version Matrix
TEG is composed of multiple components: Envoy Gateway, Envoy, Redis, Rate limit service, and the Built on Envoy composer dynamic module (which provides the WAF). The following version of each is used by each version of TEG:
| TEG Version | Envoy Gateway | Envoy | ratelimit service | BOE composer |
|---|---|---|---|---|
| v0.1.0 | v0.5.0 | v1.27-latest | v1.4.0 | — |
| v1.0.0 | v1.0.1 | distroless-v1.29.2 | 19f2079f | — |
| v1.0.1 | v1.0.2 | distroless-v1.29.5 | 19f2079f | — |
| v1.1.0 | v1.1.0 | distroless-v1.31.0 | 91484c59 | — |
| v1.2.0 | v1.2.3 | distroless-v1.32.1 | 28b1629a | — |
| v1.2.1 | v1.2.4 | distroless-v1.32.2 | 28b1629a | — |
| v1.2.2 | v1.2.5 | distroless-v1.32.3 | 49af5cca | — |
| v1.2.3 | v1.2.6 | distroless-v1.32.3 | 49af5cca | — |
| v1.2.4 | v1.2.7 | distroless-v1.32.3 | ae4cee11 | — |
| v1.2.5 | v1.2.8 | distroless-v1.32.4 | 0141a24f | — |
| v1.3.0 | v1.3.1 | distroless-v1.33.0 | ae4cee11 | — |
| v1.3.1 | v1.3.2 | distroless-v1.33.1 | 0141a24f | — |
| v1.4.0 | v1.4.1 | distroless-v1.34.1 | bb4dae24 | — |
| v1.4.1 | v1.4.2 | distroless-v1.34.1 | bb4dae24 | — |
| v1.5.0 | v1.5.0 | distroless-v1.35.0 | a90e0e5d | — |
| v1.5.1 | v1.5.4 | distroless-v1.35.6 | e74a664a | — |
| v1.6.1 | v1.6.1 | distroless-v1.36.3 | 99d85510 | — |
| v1.7.0 | v1.7.1 | distroless-v1.37.1 | c8765e89 | — |
| v1.7.1 | v1.7.2 | distroless-v1.37.2 | 05c08d03 | — |
| v1.7.2 | v1.7.3 | distroless-v1.37.2 | 05c08d03 | — |
| v1.8.0 | v1.8.0 | distroless-v1.38.0 | ff287602 | 0.6.0 |
| v1.8.1 | v1.8.1 | distroless-v1.38.1 | 1e50889b | 0.7.0 |
| v1.8.2 | v1.8.2 | distroless-v1.38.3 | aba2384d | 0.9.0 |
| v1.8.3 | v1.8.3 | distroless-v1.38.3 | f2fb1577 | 0.10.0 |
| v1.9.0 | v1.9.0 | distroless-v1.39.0 | 17b1956c | 0.11.0 |
Note that Tetrate does not provide production support for Redis. The Redis instance deployed by the TEG Helm chart is a great way to get started, but it is a single, non-replicated instance with no persistence, no high availability, and no backup, so it should be considered suitable for demo purposes only. For production, bring your own hardened Redis — see Rate Limiting.