It could be a matter of how you perceive what an agent is - an agent is not an entire execution plane, but rather a lightweight process polling your API for scheduled runs of flows with matching labels
so your single K8s cluster can have multiple agent processes, each polling for different labels (one for dev, another for prod labels, etc) and each corresponding to the relevant API key bound to a given Cloud tenant/user