Problem
The WorkerGroup.svelte component conditionally hides the entire config panel (including autoscaling settings) when a worker group is in agent mode.
At frontend/src/lib/components/WorkerGroup.svelte:1263:
This guard hides the config panel containing autoscaling controls. At line 1403, an info alert is shown instead:
"This group is formed with agent workers, there is no associated config."
However, the backend fully supports autoscaling for agent worker groups. The autoscaling logic in backend/windmill-autoscaling/src/autoscaling_ee.rs:61-66 queries the config table for any worker group with config->'autoscaling'->>'enabled' = 'true' and matches by worker_group name against worker_ping. Agent workers report to worker_ping via HTTP, so they are picked up by the autoscaler. The K8s integration scales deployments named windmill-workers-{worker_group}, which works for agent deployments too.
Current workaround
Users can create the autoscaling config directly via API:
POST /api/configs/update/worker__{group_name}
with the autoscaling JSON config body. But this is undiscoverable and fragile.
Proposed fix
Show the autoscaling configuration section for agent worker groups in the UI. The {#if !isAgent} guard at line 1263 should either be removed entirely or scoped more narrowly so that at minimum the autoscaling sub-panel is accessible for agent groups.
Problem
The
WorkerGroup.sveltecomponent conditionally hides the entire config panel (including autoscaling settings) when a worker group is in agent mode.At
frontend/src/lib/components/WorkerGroup.svelte:1263:{#if !isAgent}This guard hides the config panel containing autoscaling controls. At line 1403, an info alert is shown instead:
However, the backend fully supports autoscaling for agent worker groups. The autoscaling logic in
backend/windmill-autoscaling/src/autoscaling_ee.rs:61-66queries theconfigtable for any worker group withconfig->'autoscaling'->>'enabled' = 'true'and matches byworker_groupname againstworker_ping. Agent workers report toworker_pingvia HTTP, so they are picked up by the autoscaler. The K8s integration scales deployments namedwindmill-workers-{worker_group}, which works for agent deployments too.Current workaround
Users can create the autoscaling config directly via API:
with the autoscaling JSON config body. But this is undiscoverable and fragile.
Proposed fix
Show the autoscaling configuration section for agent worker groups in the UI. The
{#if !isAgent}guard at line 1263 should either be removed entirely or scoped more narrowly so that at minimum the autoscaling sub-panel is accessible for agent groups.