Today, kubectl ate get workers doesn't support -n/--namespace, -a/--atespace or -l/--selector , like kubectl ate top workers already does.
In multi-pool or multi-namespace clusters, unfiltered table output is noisy. kubectl ate get workers should support the same filtering flags as kubectl ate top workers.
kubectl ate get workers already displays NAMESPACE as its first column, so users naturally expect standard -n filtering to work when inspecting a specific WorkerPool namespace.
Today,
kubectl ate get workersdoesn't support-n/--namespace,-a/--atespaceor-l/--selector, likekubectl ate top workersalready does.In multi-pool or multi-namespace clusters, unfiltered table output is noisy. kubectl ate get workers should support the same filtering flags as kubectl ate top workers.
kubectl ate get workersalready displays NAMESPACE as its first column, so users naturally expect standard -n filtering to work when inspecting a specific WorkerPool namespace.