Migrating to Consul Connect ent-changelog-1.14.0
Version ent-changelog-1.14.0 introduces 6 breaking changes. This guide details how to update your code.
Released: 12/2/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
ports.grpcports.grpc_tlspeeringconnectPeerNamePeerEnvoy dynamic HTTP metricsCatalog's List Services (v1/catalog/services)/v1/txnBreaking Changes
●Issue #1
config: The existing `ports.grpc` configuration now only supports plain-text communication, as TLS configuration has been moved to the new `ports.grpc_tls` option.
●Issue #2
config: Default configurations for 1.14 now enable `peering` and `connect` by default.
●Issue #3
config: The default value for the gRPC TLS port has been set to 8503 in 1.14 defaults.
●Issue #4
connect: Support for Envoy 1.20 has been removed.
●Issue #5
peering: The field name `PeerName` has been renamed to `Peer` in prepared queries and exported services.
●Issue #6
xds: Service mesh failover now uses Envoy's aggregate clusters, which changes the names of some Envoy dynamic HTTP metrics.
Migration Steps
- 1If you rely on the existing `ports.grpc` for TLS traffic, you must migrate that configuration to the new `ports.grpc_tls` configuration option.
- 2Review configuration defaults if you are using default settings, as `peering` and `connect` are now enabled by default.
- 3If you use prepared queries or export services, update any code referencing `PeerName` to use `Peer` instead.
- 4If you rely on specific Envoy dynamic HTTP metrics related to service mesh failover, check the new metric names documented in the Envoy documentation.
Release Summary
This release introduces significant features around DNS-proxy support, gRPC enhancements, and extensive new functionality for cluster peering. It also contains breaking changes related to gRPC port configuration separation and the removal of older Envoy support.
Need More Details?
View the full release notes and all changes for Consul Connect ent-changelog-1.14.0.
View Full Changelog