AccessLogsConfig contains the associated default settings for all Envoy instances within the datacenter or partition
AgentService represents a service known to the agent
AgentServiceCheck is used to define a node or service level check
AgentServiceChecksInfo returns information about a Service and its checks
AgentServiceConnect represents the Connect configuration of a service.
AgentServiceConnectProxyConfig is the proxy configuration in a connect-proxy
ServiceDefinition or response.
AgentServiceRegistration is used to register a new service
AgentWeights represent optional weights for a service
CheckDefinition is used to JSON decode the Check definitions
CheckType is used to create either the CheckMonitor or the CheckTTL.
The following types are supported: Script, HTTP, TCP, Docker, TTL, GRPC, Alias, H2PING. Script,
HTTP, Docker, TCP, GRPC, and H2PING all require Interval. Only one of the types may
to be provided: TTL or Script/Interval or HTTP/Interval or TCP/Interval or
Docker/Interval or GRPC/Interval or AliasService or H2PING/Interval.
Since types like CheckHTTP and CheckGRPC derive from CheckType, there are
helper conversion methods that do the reverse conversion. ie. checkHTTP.CheckType()
The Consul API client.
ConnectAuthorizeRequest is the structure of a request to authorize
a connection.
ConnectProxyConfig describes the configuration needed for any proxy managed
or unmanaged. It describes a single logical service’s listener and optionally
upstreams and sidecar-related config for a single instance. To describe a
centralized proxy that routed traffic for multiple services, a different one
of these would be needed for each, sharing the same LogicalProxyID.
EnvoyExtension has configuration for an extension that patches Envoy resources.
ExposeConfig describes HTTP paths to expose through Envoy outside of Connect.
Users can expose individual paths and/or all HTTP/GRPC paths for checks.
HealthCheck is used to represent a single check
Locality identifies where a given entity is running.
MeshGatewayConfig controls how Mesh Gateways are configured and used
This is a struct to allow for future additions without having more free-hanging
configuration items all over the place
PeeringServiceMeta is read-only information provided from an exported peer.
Configuration of a proxy that a Client should pass requests to.
QueryOptions are used to parameterize a query
Type to hold a address and port of a service
ServiceConnect are the shared Connect settings between all service
definitions from the agent to the state store.
ServiceDefinition is used to JSON decode the Service definitions. For
documentation on specific fields see NodeService which is better documented.
Upstream represents a single upstream dependency for a service or proxy. It
describes the mechanism used to discover instances to communicate with (the
Target) as well as any potential client configuration that may be useful such
as load balancer options, timeouts etc.
Weights represent the weight used by DNS for a given status