Consul Connect Configuration Entries

Consul Connect configuration entries (service-defaults, service-resolver, service-router, service-splitter, service-intentions, mesh, proxy-defaults) that declaratively configure mesh behavior. Configuration entries are managed via the /v1/config API and via Kubernetes Custom Resource Definitions when running on Kubernetes.

API entry from apis.yml

apis.yml Raw ↑
aid: consul-connect:consul-connect-config-entries
name: Consul Connect Configuration Entries
description: Consul Connect configuration entries (service-defaults, service-resolver, service-router,
  service-splitter, service-intentions, mesh, proxy-defaults) that declaratively configure mesh behavior.
  Configuration entries are managed via the /v1/config API and via Kubernetes Custom Resource Definitions
  when running on Kubernetes.
humanURL: https://developer.hashicorp.com/consul/docs/connect/config-entries
baseURL: https://developer.hashicorp.com
tags:
- Configuration Entries
- CRD
- Kubernetes
- L7 Routing
properties:
- type: Documentation
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-defaults
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-router
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-splitter
x-features:
- service-defaults to set protocol and timeouts
- service-router for L7 path/header/method routing
- service-splitter for canary and blue/green rollouts
- service-resolver for failover and subsets
- mesh-wide configuration via the mesh entry
- Kubernetes CRDs for declarative mesh management
x-useCases:
- Implementing canary deployments via service-splitter
- Routing traffic by header for tenant isolation
- Centralizing TLS and protocol defaults