api: static bootstrap proto definition. (#97)
This patch adds a static bootstrap proto that is expected to be provided on the filesystem or command-line. This should enable Envoy to then either fetch the rest of config from disk or reach out to the various management servers for the rest of the APIs. Fixes #93.pull/99/head
parent
89c068ddbd
commit
8047d57891
5 changed files with 83 additions and 20 deletions
@ -0,0 +1,27 @@ |
||||
// This proto is expected to be provided on disk or via the command-line to |
||||
// Envoy. It provides sufficient information for Envoy to fetch the rest of |
||||
// its configuration from either disk or management server(s). |
||||
|
||||
syntax = "proto3"; |
||||
|
||||
package envoy.api.v2; |
||||
|
||||
import "api/base.proto"; |
||||
import "api/cds.proto"; |
||||
|
||||
message Bootstrap { |
||||
// Node identity to present to the management server and for instance |
||||
// identification purposes (e.g. in generated headers). |
||||
Node node = 1; |
||||
// All Listeners are provided by a single LDS configuration source. |
||||
ConfigSource lds_config = 2; |
||||
// All post-bootstrap Cluster definitions are provided by a single CDS |
||||
// configuration source. |
||||
ConfigSource cds_config = 3; |
||||
// If a network based configuration source is specified for cds_config, it's |
||||
// necessary to have some initial cluster definitions available to allow Envoy |
||||
// to know how to speak to the management server. These cluster definitions |
||||
// may not use EDS (i.e. they should be static IP or DNS-based). |
||||
repeated Cluster bootstrap_clusters = 4; |
||||
// TODO(htuch): Add support for HDS. |
||||
} |
Loading…
Reference in new issue