github.com/projectcontour/contour@v1.28.2/site/content/docs/v1.19.0/configuration.md (about) 1 # Contour Configuration Reference 2 3 - [Serve Flags](#serve-flags) 4 - [Configuration File](#configuration-file) 5 - [Environment Variables](#environment-variables) 6 - [Bootstrap Config File](#bootstrap-config-file) 7 8 ## Overview 9 10 There are various ways to configure Contour, flags, the configuration file, as well as environment variables. 11 Contour has a precedence of configuration for contour serve, meaning anything configured in the config file is overridden by environment vars which are overridden by cli flags. 12 13 ## Serve Flags 14 15 The `contour serve` command is the main command which is used to watch for Kubernetes resource and process them into Envoy configuration which is then streamed to any Envoy via its xDS gRPC connection. 16 There are a number of flags that can be passed to this command which further configures how Contour operates. 17 Many of these flags are mirrored in the [Contour Configuration File](#configuration-file). 18 19 | Flag Name | Description | 20 | -------------------------------------------------------- | ---------------------------------------------------------------------- | 21 | `--config-path` | Path to base configuration | 22 | `--contour-config-name` | Name of the ContourConfiguration resource to use | 23 | `--incluster` | Use in cluster configuration | 24 | `--kubeconfig=</path/to/file>` | Path to kubeconfig (if not in running inside a cluster) | 25 | `--xds-address=<ipaddr>` | xDS gRPC API address | 26 | `--xds-port=<port>` | xDS gRPC API port | 27 | `--stats-address=<ipaddr>` | Envoy /stats interface address | 28 | `--stats-port=<port>` | Envoy /stats interface port | 29 | `--debug-http-address=<address>` | Address the debug http endpoint will bind to. | 30 | `--debug-http-port=<port>` | Port the debug http endpoint will bind to | 31 | `--http-address=<ipaddr>` | Address the metrics HTTP endpoint will bind to | 32 | `--http-port=<port>` | Port the metrics HTTP endpoint will bind to. | 33 | `--health-address=<ipaddr>` | Address the health HTTP endpoint will bind to | 34 | `--health-port=<port>` | Port the health HTTP endpoint will bind to | 35 | `--contour-cafile=</path/to/file\|CONTOUR_CERT_FILE>` | CA bundle file name for serving gRPC with TLS | 36 | `--contour-cert-file=</path/to/file\|CONTOUR_CERT_FILE>` | Contour certificate file name for serving gRPC over TLS | 37 | `--contour-key-file=</path/to/file\|CONTOUR_KEY_FILE>` | Contour key file name for serving gRPC over TLS | 38 | `--insecure` | Allow serving without TLS secured gRPC | 39 | `--root-namespaces=<ns,ns>` | Restrict contour to searching these namespaces for root ingress routes | 40 | `--ingress-class-name=<name>` | Contour IngressClass name | 41 | `--ingress-status-address=<address>` | Address to set in Ingress object status | 42 | `--envoy-http-access-log=</path/to/file>` | Envoy HTTP access log | 43 | `--envoy-https-access-log=</path/to/file>` | Envoy HTTPS access log | 44 | `--envoy-service-http-address=<ipaddr>` | Kubernetes Service address for HTTP requests | 45 | `--envoy-service-https-address=<ipaddr>` | Kubernetes Service address for HTTPS requests | 46 | `--envoy-service-http-port=<port>` | Kubernetes Service port for HTTP requests | 47 | `--envoy-service-https-port=<port>` | Kubernetes Service port for HTTPS requests | 48 | `--envoy-service-name=<name>` | Name of the Envoy service to inspect for Ingress status details. | 49 | `--envoy-service-namespace=<namespace>` | Envoy Service Namespace | 50 | `--use-proxy-protocol` | Use PROXY protocol for all listeners | 51 | `--accesslog-format=<envoy\|json>` | Format for Envoy access logs | 52 | `--disable-leader-election` | Disable leader election mechanism | 53 | `-d, --debug` | Enable debug logging | 54 | `--kubernetes-debug=<log level>` | Enable Kubernetes client debug logging | 55 56 ## Configuration File 57 58 A configuration file can be passed to the `--config-path` argument of the `contour serve` command to specify additional configuration to Contour. 59 In most deployments, this file is passed to Contour via a ConfigMap which is mounted as a volume to the Contour pod. 60 61 The Contour configuration file is optional. 62 In its absence, Contour will operate with reasonable defaults. 63 Where Contour settings can also be specified with command-line flags, the command-line value takes precedence over the configuration file. 64 65 | Field Name | Type | Default | Description | 66 | ------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 67 | accesslog-format | string | `envoy` | This key sets the global [access log format][2] for Envoy. Valid options are `envoy` or `json`. | 68 | accesslog-format-string | string | None | If present, this specifies custom access log format for Envoy. See [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage) for more information about the syntax. This field only has effect if `accesslog-format` is `envoy` | 69 | debug | boolean | `false` | Enables debug logging. | 70 | default-http-versions | string array | <code style="white-space:nowrap">HTTP/1.1</code> <br> <code style="white-space:nowrap">HTTP/2</code> | This array specifies the HTTP versions that Contour should program Envoy to serve. HTTP versions are specified as strings of the form "HTTP/x", where "x" represents the version number. | 71 | disableAllowChunkedLength | boolean | `false` | If this field is true, Contour will disable the RFC-compliant Envoy behavior to strip the `Content-Length` header if `Transfer-Encoding: chunked` is also set. This is an emergency off-switch to revert back to Envoy's default behavior in case of failures. | 72 | disablePermitInsecure | boolean | `false` | If this field is true, Contour will ignore `PermitInsecure` field in HTTPProxy documents. | 73 | envoy-service-name | string | `envoy` | This sets the service name that will be inspected for address details to be applied to Ingress objects. | 74 | envoy-service-namespace | string | `projectcontour` | This sets the namespace of the service that will be inspected for address details to be applied to Ingress objects. If the `CONTOUR_NAMESPACE` environment variable is present, Contour will populate this field with its value. | 75 | ingress-status-address | string | None | If present, this specifies the address that will be copied into the Ingress status for each Ingress that Contour manages. It is exclusive with `envoy-service-name` and `envoy-service-namespace`. | 76 | incluster | boolean | `false` | This field specifies that Contour is running in a Kubernetes cluster and should use the in-cluster client access configuration. | 77 | json-fields | string array | [fields][5] | This is the list the field names to include in the JSON [access log format][2]. This field only has effect if `accesslog-format` is `json`. | 78 | kubeconfig | string | `$HOME/.kube/config` | Path to a Kubernetes [kubeconfig file][3] for when Contour is executed outside a cluster. | 79 | leaderelection | leaderelection | | The [leader election configuration](#leader-election-configuration). | 80 | policy | PolicyConfig | | The default [policy configuration](#policy-configuration). | 81 | tls | TLS | | The default [TLS configuration](#tls-configuration). | 82 | timeouts | TimeoutConfig | | The [timeout configuration](#timeout-configuration). | 83 | cluster | ClusterConfig | | The [cluster configuration](#cluster-configuration). | 84 | network | NetworkConfig | | The [network configuration](#network-configuration). | 85 | listener | ListenerConfig | | The [listener configuration](#listener-configuration). | 86 | server | ServerConfig | | The [server configuration](#server-configuration) for `contour serve` command. | 87 | gateway | GatewayConfig | | The [gateway-api Gateway configuration](#gateway-configuration). | 88 | rateLimitService | RateLimitServiceConfig | | The [rate limit service configuration](#rate-limit-service-configuration). | 89 | enableExternalNameService | boolean | `false` | Enable ExternalName Service processing. Enabling this has security implications. Please see the [advisory](https://github.com/projectcontour/contour/security/advisories/GHSA-5ph6-qq5x-7jwc) for more details. | 90 91 ### TLS Configuration 92 93 The TLS configuration block can be used to configure default values for how 94 Contour should provision TLS hosts. 95 96 | Field Name | Type | Default | Description | 97 | ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 98 | minimum-protocol-version | string | `1.2` | This field specifies the minimum TLS protocol version that is allowed. Valid options are `1.2` (default) and `1.3`. Any other value defaults to TLS 1.2. | 99 | fallback-certificate | | | [Fallback certificate configuration](#fallback-certificate). | 100 | envoy-client-certificate | | | [Client certificate configuration for Envoy](#envoy-client-certificate). | 101 | cipher-suites | []string | See [config package documentation](https://pkg.go.dev/github.com/projectcontour/contour/pkg/config#pkg-variables) | This field specifies the TLS ciphers to be supported by TLS listeners when negotiating TLS 1.2. This parameter should only be used by advanced users. Note that this is ignored when TLS 1.3 is in use. The set of ciphers that are allowed is a superset of those supported by default in stock, non-FIPS Envoy builds and FIPS builds as specified [here](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/transport_sockets/tls/v3/common.proto#envoy-v3-api-field-extensions-transport-sockets-tls-v3-tlsparameters-cipher-suites). Custom ciphers not accepted by Envoy in a standard build are not supported. | 102 103 ### Fallback Certificate 104 105 | Field Name | Type | Default | Description | 106 | ---------- | ------ | ------- | ----------------------------------------------------------------------------------------------- | 107 | name | string | `""` | This field specifies the name of the Kubernetes secret to use as the fallback certificate. | 108 | namespace | string | `""` | This field specifies the namespace of the Kubernetes secret to use as the fallback certificate. | 109 110 111 ### Envoy Client Certificate 112 113 | Field Name | Type | Default | Description | 114 | ---------- | ------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 115 | name | string | `""` | This field specifies the name of the Kubernetes secret to use as the client certificate and private key when establishing TLS connections to the backend service. | 116 | namespace | string | `""` | This field specifies the namespace of the Kubernetes secret to use as the client certificate and private key when establishing TLS connections to the backend service. | 117 118 ### Leader Election Configuration 119 120 The leader election configuration block configures how a deployment with more than one Contour pod elects a leader. 121 The Contour leader is responsible for updating the status field on Ingress and HTTPProxy documents. 122 In the vast majority of deployments, only the `configmap-name` and `configmap-namespace` fields should require any configuration. 123 124 | Field Name | Type | Default | Description | 125 | ------------------- | ------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 126 | configmap-name | string | `leader-elect` | The name of the ConfigMap that Contour leader election will lease. | 127 | configmap-namespace | string | `projectcontour` | The namespace of the ConfigMap that Contour leader election will lease. If the `CONTOUR_NAMESPACE` environment variable is present, Contour will populate this field with its value. | 128 | lease-duration | [duration][4] | `15s` | The duration of the leadership lease. | 129 | renew-deadline | [duration][4] | `10s` | The length of time that the leader will retry refreshing leadership before giving up. | 130 | retry-period | [duration][4] | `2s` | The interval at which Contour will attempt to the acquire leadership lease. | 131 132 ### Timeout Configuration 133 134 The timeout configuration block can be used to configure various timeouts for the proxies. All fields are optional; Contour/Envoy defaults apply if a field is not specified. 135 136 | Field Name | Type | Default | Description | 137 | -------------------------------- | ------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 138 | request-timeout | string | none* | This field specifies the default request timeout. Note that this is a timeout for the entire request, not an idle timeout. Must be a [valid Go duration string][4], or omitted or set to `infinity` to disable the timeout entirely. See [the Envoy documentation][12] for more information.<br /><br />_Note: A value of `0s` previously disabled this timeout entirely. This is no longer the case. Use `infinity` or omit this field to disable the timeout._ | 139 | connection-idle-timeout | string | `60s` | This field defines how long the proxy should wait while there are no active requests (for HTTP/1.1) or streams (for HTTP/2) before terminating an HTTP connection. The timeout applies to downstream connections only. Must be a [valid Go duration string][4], or `infinity` to disable the timeout entirely. See [the Envoy documentation][8] for more information. | 140 | stream-idle-timeout | string | `5m`* | This field defines how long the proxy should wait while there is no activity during single request/response (for HTTP/1.1) or stream (for HTTP/2). Timeout will not trigger while HTTP/1.1 connection is idle between two consecutive requests. Must be a [valid Go duration string][4], or `infinity` to disable the timeout entirely. See [the Envoy documentation][9] for more information. | 141 | max-connection-duration | string | none* | This field defines the maximum period of time after an HTTP connection has been established from the client to the proxy before it is closed by the proxy, regardless of whether there has been activity or not. Must be a [valid Go duration string][4], or omitted or set to `infinity` for no max duration. See [the Envoy documentation][10] for more information. | 142 | delayed-close-timeout | string | `1s`* | *Note: this is an advanced setting that should not normally need to be tuned.* <br /><br /> This field defines how long envoy will wait, once connection close processing has been initiated, for the downstream peer to close the connection before Envoy closes the socket associated with the connection. Setting this timeout to 'infinity' will disable it. See [the Envoy documentation][13] for more information. | 143 | connection-shutdown-grace-period | string | `5s`* | This field defines how long the proxy will wait between sending an initial GOAWAY frame and a second, final GOAWAY frame when terminating an HTTP/2 connection. During this grace period, the proxy will continue to respond to new streams. After the final GOAWAY frame has been sent, the proxy will refuse new streams. Must be a [valid Go duration string][4]. See [the Envoy documentation][11] for more information. | 144 145 _This is Envoy's default setting value and is not explicitly configured by Contour._ 146 147 ### Cluster Configuration 148 149 The cluster configuration block can be used to configure various parameters for Envoy clusters. 150 151 | Field Name | Type | Default | Description | 152 | ----------------- | ------ | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 153 | dns-lookup-family | string | auto | This field specifies the dns-lookup-family to use for upstream requests to externalName type Kubernetes services from an HTTPProxy route. Values are: `auto`, `v4, `v6` | 154 155 ### Network Configuration 156 157 The network configuration block can be used to configure various parameters network connections. 158 159 | Field Name | Type | Default | Description | 160 | ---------------- | ---- | ------- | ----------------------------------------------------------------------------------------------------------------------- | 161 | num-trusted-hops | int | 0 | Configures the number of additional ingress proxy hops from the right side of the x-forwarded-for HTTP header to trust. | 162 | admin-port | int | 9001 | Configures the Envoy Admin read-only listener on Envoy. Set to `0` to disable. | 163 164 ### Listener Configuration 165 166 The listener configuration block can be used to configure various parameters for Envoy listener. 167 168 | Field Name | Type | Default | Description | 169 | ------------------- | ------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 170 | connection-balancer | string | `""` | This field specifies the listener connection balancer. If the value is `exact`, the listener will use the exact connection balancer to balance connections between threads in a single Envoy process. See [the Envoy documentation][14] for more information. | 171 172 ### Server Configuration 173 174 The server configuration block can be used to configure various settings for the `contour serve` command. 175 176 | Field Name | Type | Default | Description | 177 | --------------- | ------ | ------- | ----------------------------------------------------------------------------- | 178 | xds-server-type | string | contour | This field specifies the xDS Server to use. Options are `contour` or `envoy`. | 179 180 ### Gateway Configuration 181 182 The gateway configuration block is used to configure which gateway-api Gateway Contour should configure: 183 184 | Field Name | Type | Default | Description | 185 | -------------- | ------ | ------- | ------------------------------------------------------------------------------ | 186 | controllerName | string | | Gateway Class controller name (i.e. projectcontour.io/projectcontour/contour). | 187 188 ### Policy Configuration 189 190 The Policy configuration block can be used to configure default policy values 191 that are set if not overridden by the user. 192 193 The `request-headers` field is used to rewrite headers on a HTTP request, and 194 the `response-headers` field is used to rewrite headers on a HTTP response. 195 196 | Field Name | Type | Default | Description | 197 | ---------------- | ------------ | ------- | ------------------------------------------------------------------------------------------------- | 198 | request-headers | HeaderPolicy | none | The default request headers set or removed on all service routes if not overridden in the object | 199 | response-headers | HeaderPolicy | none | The default response headers set or removed on all service routes if not overridden in the object | 200 | applyToIngress | Boolean | false | Whether the global policy should apply to Ingress objects | 201 202 #### HeaderPolicy 203 204 The `set` field sets an HTTP header value, creating it if it doesn't already exist but not overwriting it if it does. 205 The `remove` field removes an HTTP header. 206 207 | Field Name | Type | Default | Description | 208 | ---------- | ----------------- | ------- | ------------------------------------------------------------------------------- | 209 | set | map[string]string | none | Map of headers to set on all service routes if not overridden in the object | 210 | remove | []string | none | List of headers to remove on all service routes if not overridden in the object | 211 212 Note: the values of entries in the `set` and `remove` fields can be overridden in HTTPProxy objects but it it not possible to remove these entries. 213 214 ### Rate Limit Service Configuration 215 216 The rate limit service configuration block is used to configure an optional global rate limit service: 217 218 | Field Name | Type | Default | Description | 219 | ----------------------- | ------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 220 | extensionService | string | <none> | This field identifies the extension service defining the rate limit service, formatted as <namespace>/<name>. | 221 | domain | string | contour | This field defines the rate limit domain value to pass to the rate limit service. Acts as a container for a set of rate limit definitions within the RLS. | 222 | failOpen | bool | false | This field defines whether to allow requests to proceed when the rate limit service fails to respond with a valid rate limit decision within the timeout defined on the extension service. | 223 | enableXRateLimitHeaders | bool | false | This field defines whether to include the X-RateLimit headers X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (as defined by the IETF Internet-Draft https://tools.ietf.org/id/draft-polli-ratelimit-headers-03.html), on responses to clients when the Rate Limit Service is consulted for a request. | 224 225 ### Configuration Example 226 227 The following is an example ConfigMap with configuration file included: 228 229 ```yaml 230 apiVersion: v1 231 kind: ConfigMap 232 metadata: 233 name: contour 234 namespace: projectcontour 235 data: 236 contour.yaml: | 237 # 238 # server: 239 # determine which XDS Server implementation to utilize in Contour. 240 # xds-server-type: contour 241 # 242 # specify the gateway-api Gateway Contour should configure 243 # gateway: 244 # controllerName: projectcontour.io/projectcontour/contour 245 # 246 # should contour expect to be running inside a k8s cluster 247 # incluster: true 248 # 249 # path to kubeconfig (if not running inside a k8s cluster) 250 # kubeconfig: /path/to/.kube/config 251 # 252 # Disable RFC-compliant behavior to strip "Content-Length" header if 253 # "Tranfer-Encoding: chunked" is also set. 254 # disableAllowChunkedLength: false 255 # Disable HTTPProxy permitInsecure field 256 disablePermitInsecure: false 257 tls: 258 # minimum TLS version that Contour will negotiate 259 # minimum-protocol-version: "1.2" 260 # TLS ciphers to be supported by Envoy TLS listeners when negotiating 261 # TLS 1.2. 262 # cipher-suites: 263 # - '[ECDHE-ECDSA-AES128-GCM-SHA256|ECDHE-ECDSA-CHACHA20-POLY1305]' 264 # - '[ECDHE-RSA-AES128-GCM-SHA256|ECDHE-RSA-CHACHA20-POLY1305]' 265 # - 'ECDHE-ECDSA-AES256-GCM-SHA384' 266 # - 'ECDHE-RSA-AES256-GCM-SHA384' 267 # Defines the Kubernetes name/namespace matching a secret to use 268 # as the fallback certificate when requests which don't match the 269 # SNI defined for a vhost. 270 fallback-certificate: 271 # name: fallback-secret-name 272 # namespace: projectcontour 273 envoy-client-certificate: 274 # name: envoy-client-cert-secret-name 275 # namespace: projectcontour 276 # The following config shows the defaults for the leader election. 277 # leaderelection: 278 # configmap-name: leader-elect 279 # configmap-namespace: projectcontour 280 ### Logging options 281 # Default setting 282 accesslog-format: envoy 283 # The default access log format is defined by Envoy but it can be customized by setting following variable. 284 # accesslog-format-string: "...\n" 285 # To enable JSON logging in Envoy 286 # accesslog-format: json 287 # The default fields that will be logged are specified below. 288 # To customise this list, just add or remove entries. 289 # The canonical list is available at 290 # https://godoc.org/github.com/projectcontour/contour/internal/envoy#JSONFields 291 # json-fields: 292 # - "@timestamp" 293 # - "authority" 294 # - "bytes_received" 295 # - "bytes_sent" 296 # - "downstream_local_address" 297 # - "downstream_remote_address" 298 # - "duration" 299 # - "method" 300 # - "path" 301 # - "protocol" 302 # - "request_id" 303 # - "requested_server_name" 304 # - "response_code" 305 # - "response_flags" 306 # - "uber_trace_id" 307 # - "upstream_cluster" 308 # - "upstream_host" 309 # - "upstream_local_address" 310 # - "upstream_service_time" 311 # - "user_agent" 312 # - "x_forwarded_for" 313 # 314 # default-http-versions: 315 # - "HTTP/2" 316 # - "HTTP/1.1" 317 # 318 # The following shows the default proxy timeout settings. 319 # timeouts: 320 # request-timeout: infinity 321 # connection-idle-timeout: 60s 322 # stream-idle-timeout: 5m 323 # max-connection-duration: infinity 324 # connection-shutdown-grace-period: 5s 325 # 326 # Envoy cluster settings. 327 # cluster: 328 # configure the cluster dns lookup family 329 # valid options are: auto (default), v4, v6 330 # dns-lookup-family: auto 331 # 332 # network: 333 # Configure the number of additional ingress proxy hops from the 334 # right side of the x-forwarded-for HTTP header to trust. 335 # num-trusted-hops: 0 336 # Configure the port used to access the Envoy Admin interface. 337 # admin-port: 9001 338 # 339 # Configure an optional global rate limit service. 340 # rateLimitService: 341 # Identifies the extension service defining the rate limit service, 342 # formatted as <namespace>/<name>. 343 # extensionService: projectcontour/ratelimit 344 # Defines the rate limit domain to pass to the rate limit service. 345 # Acts as a container for a set of rate limit definitions within 346 # the RLS. 347 # domain: contour 348 # Defines whether to allow requests to proceed when the rate limit 349 # service fails to respond with a valid rate limit decision within 350 # the timeout defined on the extension service. 351 # failOpen: false 352 # Defines whether to include the X-RateLimit headers X-RateLimit-Limit, 353 # X-RateLimit-Remaining, and X-RateLimit-Reset (as defined by the IETF 354 # Internet-Draft linked below), on responses to clients when the Rate 355 # Limit Service is consulted for a request. 356 # ref. https://tools.ietf.org/id/draft-polli-ratelimit-headers-03.html 357 # enableXRateLimitHeaders: false 358 # 359 # Global Policy settings. 360 # policy: 361 # # Default headers to set on all requests (unless set/removed on the HTTPProxy object itself) 362 # request-headers: 363 # set: 364 # # example: the hostname of the Envoy instance that proxied the request 365 # X-Envoy-Hostname: %HOSTNAME% 366 # # example: add a l5d-dst-override header to instruct Linkerd what service the request is destined for 367 # l5d-dst-override: %CONTOUR_SERVICE_NAME%.%CONTOUR_NAMESPACE%.svc.cluster.local:%CONTOUR_SERVICE_PORT% 368 # # default headers to set on all responses (unless set/removed on the HTTPProxy object itself) 369 # response-headers: 370 # set: 371 # # example: Envoy flags that provide additional details about the response or connection 372 # X-Envoy-Response-Flags: %RESPONSE_FLAGS% 373 # Whether or not the policy settings should apply to ingress objects 374 # applyToIngress: true 375 # 376 ``` 377 378 _Note:_ The default example `contour` includes this [file][1] for easy deployment of Contour. 379 380 ## Environment Variables 381 382 ### CONTOUR_NAMESPACE 383 384 If present, the value of the `CONTOUR_NAMESPACE` environment variable is used as: 385 386 1. The value for the `contour bootstrap --namespace` flag unless otherwise specified. 387 1. The value for the `contour certgen --namespace` flag unless otherwise specified. 388 1. The value for the `contour serve --envoy-service-namespace` flag unless otherwise specified. 389 1. The value for the `leaderelection.configmap-namespace` config file setting for `contour serve` unless otherwise specified. 390 391 The `CONTOUR_NAMESPACE` environment variable is set via the [Downward API][6] in the Contour [example manifests][7]. 392 393 ## Bootstrap Config File 394 395 The bootstrap configuration file is generated by an initContainer in the Envoy daemonset which runs the `contour bootstrap` command to generate the file. 396 This configuration file configures the Envoy container to connect to Contour and receive configuration via xDS. 397 398 The next section outlines all the available flags that can be passed to the `contour bootstrap` command which are used to customize 399 the configuration file to match the environment in which Envoy is deployed. 400 401 ### Flags 402 403 There are flags that can be passed to `contour bootstrap` that help configure how Envoy 404 connects to Contour: 405 406 | Flag | Default | Description | 407 | -------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 408 | <nobr>--resources-dir</nobr> | "" | Directory where resource files will be written. | 409 | <nobr>--admin-address</nobr> | /admin/admin.sock | Path to Envoy admin unix domain socket. | 410 | <nobr>--admin-port (Deprecated)</nobr> | 9001 | Deprecated: Port is now configured as a Contour flag. | 411 | <nobr>--xds-address</nobr> | 127.0.0.1 | Address to connect to Contour xDS server on. | 412 | <nobr>--xds-port</nobr> | 8001 | Port to connect to Contour xDS server on. | 413 | <nobr>--envoy-cafile</nobr> | "" | CA filename for Envoy secure xDS gRPC communication. | 414 | <nobr>--envoy-cert-file</nobr> | "" | Client certificate filename for Envoy secure xDS gRPC communication. | 415 | <nobr>--envoy-key-file</nobr> | "" | Client key filename for Envoy secure xDS gRPC communication. | 416 | <nobr>--namespace</nobr> | projectcontour | Namespace the Envoy container will run, also configured via ENV variable "CONTOUR_NAMESPACE". Namespace is used as part of the metric names on static resources defined in the bootstrap configuration file. | 417 | <nobr>--xds-resource-version</nobr> | v3 | Currently, the only valid xDS API resource version is `v3`. | 418 | <nobr>--dns-lookup-family</nobr> | auto | Defines what DNS Resolution Policy to use for Envoy -> Contour cluster name lookup. Either v4, v6 or auto. | 419 420 421 [1]: {{< param github_url>}}/tree/{{< param version >}}/examples/contour/01-contour-config.yaml 422 [2]: /guides/structured-logs 423 [3]: https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/ 424 [4]: https://golang.org/pkg/time/#ParseDuration 425 [5]: https://godoc.org/github.com/projectcontour/contour/internal/envoy#DefaultFields 426 [6]: https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/ 427 [7]: {{< param github_url>}}/tree/{{< param version >}}/examples/contour 428 [8]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-field-config-core-v3-httpprotocoloptions-idle-timeout 429 [9]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-stream-idle-timeout 430 [10]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#envoy-v3-api-field-config-core-v3-httpprotocoloptions-max-connection-duration 431 [11]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-drain-timeout 432 [12]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-request-timeout 433 [13]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-delayed-close-timeout 434 [14]: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/listener/v3/listener.proto#config-listener-v3-listener-connectionbalanceconfig