#6996 fix: set explicit 5-minute timeout on TaskAction watch Pull request opened by pingsutw Why are the changes needed? Without an explicit

TimeoutSeconds

, the K8s API server uses a short default timeout (~30s) for watch connections. This causes the TaskAction watcher to reconnect every ~30 seconds, producing noisy warning logs:

{
  "json": {
    "src": "client.go:356"
  },
  "level": "warning",
  "msg": "Watch error, will retry: watch channel closed"
}

What changes were proposed in this pull request? Set

TimeoutSeconds

to 300 (5 minutes) on the TaskAction watch in

actions/k8s/client.go

. This reduces unnecessary reconnections and log spam while staying well within the etcd compaction window. How was this patch tested? Manual verification — the watch reconnection logic is unchanged, only the interval between reconnections is extended. Labels • fixed: Reduces noisy watch reconnection logs. Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. flyteorg/flyte