Multiport feature support
Enterprise
This feature requires Consul Enterprise. Refer to the enterprise feature matrix for additional information.
This page summarizes the support status of Consul service mesh features when used with multiport services.
Feature support matrix
| Feature | Status | Description |
|---|---|---|
| Cross-partition | Yes | Validated for Kubernetes with Consul admin partitions. Other platforms aren't separately validated. |
| Cluster peering | No | Not currently supported. |
| Upstream: transparent proxy mode | Yes | — |
| Upstream: non-transparent proxy mode | Yes | — |
| Multi-protocol (L7) | Yes | Supported for the default port. Named, non-default ports connect directly to the destination port instead of traversing the chain. |
| API gateway | No | Not currently supported. |
| Terminating gateway | No | Not currently supported. |
| Ingress gateway | No | Ingress gateway is deprecated. |
| Discovery chain: splitter, resolver, and router | Yes | Supported for the default port. Failover and redirects are also supported at the default port level only. Non-default named ports connect directly to the destination port instead of being routed through the chain. |
| Proxy and service defaults: destination port | No | Not currently supported. |
| Proxy and service defaults: source port | No | Not currently supported. |
| Escape hatches, fault injection, and other overrides | No | Not currently supported. |
| Port-specific intentions (ACLs) | No | Consul recognizes service-level identity for intentions. There are no port-level intention rules. |
| Per-port TLS permissiveness override | No | Not currently supported. |
| Per-port metrics | Yes | Each named port gets its own Envoy cluster, enabling per-cluster metrics. |
| Per-port tracing | No | Distributed tracing doesn't yet include port-level tags. |
| Port-wise health checks and reconciliation | No | Not currently supported. |
| Platform: Kubernetes | Yes | — |
| Platform: ECS, ESM, and Terraform modules | No | Not currently supported. |
| DNS compatibility | Yes | Named ports resolve via DNS SRV lookups. Other DNS record types don't carry port-level information. |
| DNS: localized DNS | No | Not currently supported. |
| DNS: prepared queries | No | Not currently supported. |
| Passthrough mode (transparent proxy) | No | Passthrough mode uses Envoy's original destination cluster to route traffic without modifying the destination. This hasn't been separately validated for multiport services. |