One familiar, one pod?
Every few months a coven asks whether each familiar should run in its own pod. The instinct is understandable. Isolation feels safe, and a cat with its own pod at least cannot knock over anyone else's cauldron.
In practice, most familiars are better scheduled together. A shared pod keeps message latency low, makes snack forecasting simpler and spares the platform team four hundred near-identical manifests, one per owl. It also leaves one restart policy to reason about instead of one per species.
There are three exceptions. Familiars that guard forbidden names belong on their own, behind a two-wizard read. Familiars with unpredictable moods should be isolated, so their restarts do not cascade. And any bound imp running batch work gets its own pod, because it is almost certainly scheming.