The term _controller_ has a specific meaning in Kubernetes context, and this process doesn't really fit it. It doesn't monitor any Kubernetes resources, custom or otherwise. It does use Kubernetes as a data store (via the lease), but I don't really think that counts. Anyway, the term _coordinator_ fits better in my opinion. |
||
---|---|---|
.. | ||
basic.rs | ||
lock.rs | ||
main.rs |