Get desktop application:
View/edit binary Protocol Buffers messages
Given a destination, return all addresses in that destination as a long- running stream of updates.
A new set of endpoints are available for the service. The set might be empty.
Some endpoints have been removed from the service.
`no_endpoints{exists: false}` indicates that the service does not exist and the client MAY try an alternate service discovery method (e.g. DNS). `no_endpoints(exists: true)` indicates that the service does exist and the client MUST NOT fall back to an alternate service discovery method.
Given a destination, return that destination's profile and send an update whenever it changes.
The fully-qualified service name, if one exists. When resolving (especially by IP), this field provides the fully-qualified name of the resolved service, if one exists. This field does NOT include any port information. E.g. a lookup for 10.2.3.4:8080 might have a name like `foo.bar.svc.cluster.local`. Implementations MAY provide names for non-service IP-lookups (e.g., pod or node dns names), but this is not required. If the lookup does not refer to a known named entity, this field MUST be left empty.
Indicates that connections on this service address should be handled as opaque TCP streams. HTTP routes returned on for such services will be ignored.
A list of routes, each with a RequestMatch. If a request matches more than one route, the first match wins.
The retry budget controls how much additional load the proxy can generate as retries. Failured requests on retryable routes will not be retried if there is no available budget.
If this list is non-empty, requests to this destination should instead be split between the destinations in this list. Each destination should receive a portion of the requests proportional to its weight. If this list is empty, requests should be sent to this destination as normal.
If this field is set, it indicates that the target is a known endpoint (and not a service address). The values of `fully_qualified_name` and `dst_overrides` will be ignored for the purposes of service discovery-- traffic split and load balancing will be skipped and the single endpoint are used. No endpoint should be set If the target is unknown.
A reference to the metadata for this destination, usually a service. May be omitted if the destination is not a service.
A reference to the metadata for a ServiceProfile resource. This is omitted when no ServiceProfile resource exists.
Used in:
Used in:
Used as request type in: Destination.Get, Destination.GetProfile
An opaque value that is set at injection-time and sent with destintion lookups. If, for instance, the token encodes a namespace or some locality information, the service may alter its results to take this locality into account.
Configures the parameters used to initialize an HTTP/2 connection.
Used in:
Overrides the default client flow control settings.
Enables keep-alive timeouts.
Configures Hyper internals.
Used in:
Configures the maximum connection-level flow control window size.
Configures the maximum stream-level flow control window size.
Enables Hyper's adaptive flow control, ignoring other window settings.
Used in:
Used in:
The time between pings.
The time to wait for a ping response before considering the connection dead.
Whether to send pings when there is no other traffic.
If either a minimum or maximum is not specified, the range is considered to be over a discrete value.
Used in:
Minimum matching http status code (inclusive), if specified.
Maximum matching http status code (inclusive), if specified.
Used in:
Used in:
Match if the request path matches this regex.
A hint of what protocol the service knows. The default value is for the `hint` field to be not be set, essentially meaning "unknown".
Used in:
Hints that the service understands HTTP2 and the proxy's internal http2-upgrade mechanism.
Hints that the destination will handle this connection as an opaque TCP stream, and (if `opaque_transport` is set) that the proxy should not send a `SessionProtocol` as part of its transport header.
When set, indicates that the target supports receiving opaque traffic wrapped with the Linkerd connection header on the specified port.
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
The target proxy's inbound port.
Used in: ,
TODO: match on arbitrary header
Used in:
Used in:
This class contains responses which match this condition.
If responses in this class should be considered failures. This defaults to false (success).
Used in: ,
TODO: match on arbitrary header or trailer
Used in:
Used in:
The ratio of additional traffic that may be added by retries. A retry_ratio of 0.1 means that 1 retry may be attempted for every 10 regular requests. A retry_ratio of 1.0 means that 1 retry may be attempted for every 1 regular request (in other words, total request load may be doubled as a result of retries).
The proxy may always attempt this number of retries per second, even if it would violate the retry_ratio. This is to allow retries to happen even when the request rate is very low.
This duration indicates for how long requests should be considered for the purposes of enforcing the retry_ratio. A higher value considers a larger window and therefore allows burstier retries.
Used in:
This route contains requests which match this condition.
A list of response classes for this route. If a response matches more than one ResponseClass, the first match wins. If a response does not match any ResponseClasses, it is considered to be a successful response.
Metric labels to attach to requests and responses that match this route.
If a route is retryable, any failed requests on that route may be retried by the proxy.
After this time has elapsed since receiving the initial request, any outstanding request will be cancelled, a timeout error response will be returned, and no more retries will be attempted.
Used in:
The server name of the endpoint. This is the value that needs to be included by clients in the ClientHello SNI extension of the TLS handshake when they initiate TLS connections to servers.
Verify the certificate based on the Kubernetes pod identity.
Used in:
A DNS-like name that encodes workload coordinates. For example: {name}.{namespace}.{type}.identity.{control-namespace}.{trust-domain...}
Verify the certificate based on an URI identity.
Used in:
A URI name that encodes workload identity. For example: spiffe://trust-domain/workload-dentifier
Used in: , ,
The HTTP/2 parameters to use when connecting to the destination, if HTTP/2 is used. These parameters are used by proxies when the application traffic is HTTP/2 or when the H2 ProtocolHint is used to transport HTTP/1 connections over HTTP/2.
A reference to the metadata for this endpoint, usually a Pod. This may be omitted when the resource type is unknown.
Used in:
Used in:
This authority will be used as the `path` in a call to the Destination.Get rpc.
The proportion of requests to send to this destination. This value is relative to other weights in the same dst_overrides list.
A reference to the metadata for a Service resource.