The runtime configuration specifies the location of the local file system tree that contains re-loadable configuration elements. Values can be viewed at the /runtime admin endpoint. Values can be modified and added at the /runtime_modify admin endpoint. If runtime is not configured, an empty provider is used which has the effect of using all defaults built into the code, except for any values added via /runtime_modify.
File system layout¶
Various sections of the configuration guide describe the runtime settings that are available. For example, here are the runtime settings for upstream clusters.
Assume that the folder
/srv/runtime/v1 points to the actual file system path where global
runtime configurations are stored. The following would be a typical configuration setting for
/srv/runtime/current is a symbolic link to
Each ‘.’ in a runtime key indicates a new directory in the hierarchy, rooted at symlink_root + subdirectory. For example, the health_check.min_interval key would have the following full file system path (using the symbolic link):
The terminal portion of a path is the file. The contents of the file constitute the runtime value. When reading numeric values from a file, spaces and new lines will be ignored.
The override_subdirectory is used along with the
--service-cluster CLI option. Assume
--service-cluster has been set to
my-cluster. Envoy will first look for the
health_check.min_interval key in the following full file system path:
If found, the value will override any value found in the primary lookup path. This allows the user to customize the runtime values for individual clusters on top of global defaults.
The file system runtime provider emits some statistics in the runtime. namespace.
|Total number of load attempts that resulted in an error
|Total number of loads that did not use an override directory
|Total number of loads that did use an override directory
|Total number of load attempts that were successful
|Number of keys currently loaded