acoustic-carpenter-78188
05/05/2026, 8:58 PMLoggingContext.kubernetes_pod_name and kubernetes_container_name had a min_len = 1 buf validation constraint, which rejected label-based log requests where the caller provides pod labels instead of a specific pod name. Union Cloud's DP dataproxy uses label-based queries for multi-pod jobs (e.g. Ray) where the specific pod name is not known upfront.
TailTaskExecutionLogsResponse.Logs was also missing a container field needed by the client to attribute log lines to specific pod/container pairs in the UI dropdown.
What
• Remove min_len from LoggingContext.kubernetes_pod_name and kubernetes_container_name fields
• Add ContainerIdentifier container = 3 to TailTaskExecutionLogsResponse.Logs
• Regenerate all gen files
Testing
Verified via Union Cloud DP dataproxy integration — label-based log queries now pass proto validation and the container identifier is correctly surfaced to the client.
flyteorg/flyteacoustic-carpenter-78188
05/22/2026, 8:07 AM