Skip to content

Envoy Bootstrap Configuration

The Envoy Bootstrap Configuration defines the initial startup parameters and core architecture of the Envoy proxy within a Service mesh.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md] In Istio, this configuration is typically applied to workloads via the sidecar.istio.io/bootstrapOverride annotation.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md]

Applying Custom Configuration

To implement a custom bootstrap, the configuration is first stored in a Kubernetes ConfigMap.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md] This ConfigMap is then referenced by the application's Pod, allowing the proxy to boot with the user-defined parameters.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md]

Merging Behavior

When a custom configuration is applied, it is passed to Envoy using the --config-yaml flag.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md] The system merges this input with the default configuration according to specific rules: singular values replace the default values, while repeated values are appended to the existing configuration.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md]

Verification

Administrators can verify the active bootstrap configuration of a running Pod using the istioctl command-line tool.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md]

Sources

^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__custom-bootstrap__README.md]