package fleetspeak.components

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message AdminConfig

config.proto:220

Used in: Config

message CleartextHeaderChecksumConfig

config.proto:150

In this mode Fleetspeak runs in clear text (HTTP). This allows for Fleetspeak to be deployed in a Service Mesh behind a side car proxy that offers a secure communications channel. Fleetspeak accepts a TLS connection from an intermediate actor which terminates the TLS protocol (typically a layer 7 load balancer). The original client passes the certificate it uses for the TLS protocol to the frontend via an HTTP header. The intermediate actor passes a SHA256 checksum of client certificate it receives from the original TLS connection to the frontend via a second HTTP header. The Fleetspeak frontend uses the certificate passed passed from the client to identify it, and uses the hash from the intermediate actor to verify that this certificate was in fact used in the original TLS connection.

Used in: FrontendConfig

message CleartextHeaderConfig

config.proto:131

In this mode Fleetspeak runs in clear text (HTTP). This allows for Fleetspeak to be deployed in a Service Mesh behind a side car proxy that offers a secure communications channel. Fleetspeak accepts a TLS connection from an intermediate actor which terminates the TLS protocol (typically a layer 7 load balancer). The intermediate actor passes the client certificate it receives from the original TLS connection to the frontend via an HTTP header. The Fleetspeak frontend uses the certificate passed in this header to identify the client.

Used in: FrontendConfig

message CleartextXfccConfig

config.proto:168

In this mode Fleetspeak runs in clear text (HTTP). This allows for Fleetspeak to be deployed in a Service Mesh behind a side car proxy that offers a secure communications channel. Fleetspeak accepts a TLS connection from an intermediate envoy which terminates the mTLS protocol exchange. The intermediate envoy passes the client certificate it receives from the original mTLS connection to the frontend via an HTTP header. The Fleetspeak frontend uses the certificate passed in this header to identify the client.

Used in: FrontendConfig

message Config

config.proto:21

Used in: config.Config

message FrontendConfig

config.proto:176

The frontend config determines how the Fleetspeak frontend communicates with clients and how it identifies them.

Used in: HttpsConfig

message HealthCheckConfig

config.proto:234

Used in: Config

message HttpsConfig

config.proto:192

Used in: Config

message HttpsHeaderChecksumConfig

config.proto:113

In this mode Fleetspeak accepts a TLS connection from an intermediate actor which terminates the TLS protocol (typically a layer 7 load balancer). The original client passes the certificate it uses for the TLS protocol to the frontend via an HTTP header. The intermediate actor passes a SHA256 checksum of client certificate it receives from the original TLS connection to the frontend via a second HTTP header. The Fleetspeak frontend uses the certificate passed passed from the client to identify it, and uses the hash from the intermediate actor to verify that this certificate was in fact used in the original TLS connection.

Used in: FrontendConfig

message HttpsHeaderConfig

config.proto:97

In this mode Fleetspeak accepts a TLS connection from an intermediate actor which terminates the TLS protocol (typically a layer 7 load balancer). The intermediate actor passes the client certificate it receives from the original TLS connection to the frontend via an HTTP header. The Fleetspeak frontend uses the certificate passed in this header to identify the client.

Used in: FrontendConfig

message MTlsConfig

config.proto:89

In this mode Fleetspeak accepts a mTLS connection directly from the client. The Fleetspeak frontend uses the client certificate from the HTTPS request to identify the client. This is the default operating mode of the frontend.

Used in: FrontendConfig

(message has no fields)

message SpannerConfig

config.proto:73

Used in: Config

message StatsConfig

config.proto:226

Used in: Config