Add notes on runtime reload support to documentation
@@ -101,7 +101,7 @@ The `crio.api` table contains settings for the kubelet/gRPC interface.
The `crio.runtime` table contains settings pertaining to the OCI runtime used and options for how to set up and manage the OCI runtime.
**default_runtime**="runc"
- The _name_ of the OCI runtime to be used as the default.
+ The _name_ of the OCI runtime to be used as the default. This option supports live configuration reload.
**default_ulimits**=[]
A list of ulimits to be set in containers by default, specified as "<ulimit name>=<soft limit>:<hard limit>", for example:"nofile=1024:2048". If nothing is set here, settings will be inherited from the CRI-O daemon.
@@ -287,7 +287,7 @@ the container runtime configuration.
Enable CRIU integration, requires that the criu binary is available in $PATH. (default: false)
### CRIO.RUNTIME.RUNTIMES TABLE
-The "crio.runtime.runtimes" table defines a list of OCI compatible runtimes. The runtime to use is picked based on the runtime handler provided by the CRI. If no runtime handler is provided, the runtime will be picked based on the level of trust of the workload.
+The "crio.runtime.runtimes" table defines a list of OCI compatible runtimes. The runtime to use is picked based on the runtime handler provided by the CRI. If no runtime handler is provided, the runtime will be picked based on the level of trust of the workload. This option supports live configuration reload. Note that on reload runtimes can only be added to this table but not modified or removed.
**runtime_path**=""
Path to the OCI compatible runtime used for this runtime handler.
