Sandbox creation fails with DNS-1035 validation error when using agent-sandbox provider #389
Description
Sandbox creation fails with DNS-1035 validation error when using agent-sandbox provider
Problem
When using agent-sandbox as the workload provider, sandbox creation fails due to a Kubernetes Service naming validation error. The UUID-based sandbox ID does not conform to DNS-1035 label rules (must start with an alphabetic character). Additionally, the server's health endpoint becomes unresponsive, causing the Pod to be restarted.
Deployment Information
Server image: opensandbox/server:v0.1.5
config.toml
[server]
host = '0.0.0.0'
port = 8080
[runtime]
type = "kubernetes"
execd_image = "opensandbox/execd:v1.0.6"
[kubernetes]
namespace = "sandbox"
workload_provider = "agent-sandbox"
[agent_sandbox]
shutdown_policy = "Delete"Server Pod Log
INFO: 2026-03-09 05:05:15+0000 [6ab40aa2a14049f2af97e986915c4e75] src.services.k8s.kubernetes_service: Sandbox 3b1bf55e-54d1-4f14-a988-8b326355290b state: Pending - Error seen: Service "3b1bf55e-54d1-4f14-a988-8b326355290b" is invalid: metadata.name: Invalid value: "3b1bf55e-54d1-4f14-a988-8b326355290b": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name', or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')