> I don't want to write a Kubernetes controller. I don't even know why it should exist. I don't want to write one either. Given the choice, I won't even touch

> I don't want to write a Kubernetes controller. I don't even know why it should exist. I don't want to write one either. Given the choice, I won't even touch one. I think I know why they exist, though. Kubernetes is a system of actors (resources) and events (state transitions). If you want to derive new state from existing state, and to maintain that new state, then you need something that observes "lower" state transitions and takes action on the system to achieve its desired "higher" state. Whether we invent terminology for these things or not, controllers exist in all such systems.