●Change8

Migrating to Consul Connect ent-changelog-1.13.0

Version ent-changelog-1.13.0 introduces 3 breaking changes. This guide details how to update your code.

Released: 12/2/2025

3
Breaking Changes
2
Migration Steps
12
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

/catalog/node-services/:node-name API`telemetry { disable_compat_1.9 }` flagEnvoy 1.19Envoy 1.23.0acl token read CLI commandagent/self endpointconsul version command`Sign` gRPC APIUDP health checksconfig delete CLI command`service-default` config entryServerDiscovery.WatchServers gRPC endpoint

Breaking Changes

●Issue #1

config-entry: Exporting a specific service name across all namespace is invalid.

●Issue #2

connect: Support for Envoy 1.19 has been removed. Users must upgrade Envoy.

●Issue #3

telemetry: The config flag `telemetry { disable_compat_1.9 = (true|false) }` has been removed. Remove this flag from your configuration before upgrading.

Migration Steps

  1. 1
    If you are using the `telemetry { disable_compat_1.9 }` config flag, remove it from your configuration before upgrading.
  2. 2
    Ensure Envoy versions are 1.23.0 or newer, as support for 1.19 has been removed.

Release Summary

This release introduces Cluster Peering (Beta) and transparent proxying via terminating gateways, alongside numerous gRPC API enhancements and bug fixes. Consumers must remove the deprecated telemetry config flag and ensure Envoy is updated past version 1.19.

Need More Details?

View the full release notes and all changes for Consul Connect ent-changelog-1.13.0.

View Full Changelog