From ce524a395884e6cad41e1cdd68878a66b24faa76 Mon Sep 17 00:00:00 2001 From: "alex.lyn" Date: Wed, 25 Dec 2024 19:24:51 +0800 Subject: [PATCH] kata-types: Give a more comprehensive definition of request_timeout_ms To better understand the impact of different timeout values on system behavior, this section provides a more comprehensive explanation of the request_timeout_ms: This timeout value is used to set the maximum duration for the agent to process a CreateContainerRequest. It's also used to ensure that workloads, especially those involving large image pulls within the guest, have sufficient time to complete. Based on explaination above, it's renamed with `create_container_timeout`, Specially, exposed in 'configuration.toml' Fixes #10692 Signed-off-by: alex.lyn --- src/libs/kata-types/src/config/agent.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/libs/kata-types/src/config/agent.rs b/src/libs/kata-types/src/config/agent.rs index ecb03fff34..ad5a85bda7 100644 --- a/src/libs/kata-types/src/config/agent.rs +++ b/src/libs/kata-types/src/config/agent.rs @@ -112,7 +112,10 @@ pub struct Agent { pub reconnect_timeout_ms: u32, /// Agent request timeout value in millisecond - #[serde(default = "default_request_timeout")] + /// This timeout value is used to set the maximum duration for the agent to process a CreateContainerRequest. + /// It's also used to ensure that workloads, especially those involving large image pulls within the guest, + /// have sufficient time to complete. + #[serde(default = "default_request_timeout", rename = "create_container_timeout")] pub request_timeout_ms: u32, /// Agent health check request timeout value in millisecond