For users deploying ADK on Kubernetes and using GKE for Code Execution (https://google.github.io/adk-docs/tools/built-in-tools/#gke-code-executor), it would be great to leverage the faster startup latency and more granular control in Agent Sandbox (https://github.com/kubernetes-sigs/agent-sandbox)
I would like to see an additional type option in the GkeCodeExecutor which expands for the Sandbox type (https://github.com/kubernetes-sigs/agent-sandbox/blob/main/k8s/crds/agents.x-k8s.io_sandboxes.yaml). This would augment the current type: job which exists today. For backwards compatibility and stability, I'd expect the type = 'job' to be the default - at least until the Sandbox API graduates and stabilizes.
gke_executor = GkeCodeExecutor(
...
type="sandbox"
...
)
When ADK instantiates a code execution request via the GkeCodeExecutor of type sandbox, ADK will create a SandboxClaim object. Once fulfilled with a Sandbox, ADK will execute the code and return the result. K8s administrators will have the option to configure things like WarmPools for low-latency execution and SandboxTemplates for ease of use. I will expect these administrator configuration will work as expected when SandboxClaims are instantiated via GkeCodeExecutor.
For users deploying ADK on Kubernetes and using GKE for Code Execution (https://google.github.io/adk-docs/tools/built-in-tools/#gke-code-executor), it would be great to leverage the faster startup latency and more granular control in Agent Sandbox (https://github.com/kubernetes-sigs/agent-sandbox)
I would like to see an additional
typeoption in the GkeCodeExecutor which expands for theSandboxtype (https://github.com/kubernetes-sigs/agent-sandbox/blob/main/k8s/crds/agents.x-k8s.io_sandboxes.yaml). This would augment the currenttype: jobwhich exists today. For backwards compatibility and stability, I'd expect thetype = 'job'to be the default - at least until the Sandbox API graduates and stabilizes.When ADK instantiates a code execution request via the
GkeCodeExecutorof typesandbox, ADK will create aSandboxClaimobject. Once fulfilled with aSandbox, ADK will execute the code and return the result. K8s administrators will have the option to configure things like WarmPools for low-latency execution and SandboxTemplates for ease of use. I will expect these administrator configuration will work as expected whenSandboxClaimsare instantiated viaGkeCodeExecutor.