●Change8

Migrating to Consul Connect ent-changelog-1.16.0

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

Released: 12/2/2025

2
Breaking Changes
1
Migration Steps
11
Affected Symbols

⚠️ Check Your Code

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

/v1/health/connect//v1/health/ingress/service-defaultsconsul services exportAllowEnablingPermissiveMutualTLSMutualTLSModev1/operator/audit-hashconsul operator audit hashservice exportsgateway configuration objectsagent health checks

Breaking Changes

●Issue #1

The /v1/health/connect/ and /v1/health/ingress/ API endpoints now return 403 "Permission Denied" if the provided token lacks sufficient 'service:read' permissions. Previously, they returned a success code with an empty result list.

●Issue #2

Deprecated backward-compatibility behavior related to peering has been removed. Upstream overrides in service-defaults will now only apply to peer upstreams when the 'peer' field is explicitly provided.

Migration Steps

  1. 1
    Review the 1.16.x upgrade instructions regarding peering changes: Upstream overrides in service-defaults will now only apply to peer upstreams when the 'peer' field is provided. Visit https://developer.hashicorp.com/consul/docs/upgrading/upgrade-specific for more information.

Release Summary

This release introduces several new features, particularly around XDS extensions, permissive mTLS, and enterprise audit logging capabilities. It also contains breaking changes related to permission handling on specific API endpoints and removal of deprecated peering behavior.

Need More Details?

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

View Full Changelog