Kuberenetes resources have a revision number, which changes each time the
resource is modified. Also, its possible to have an operation target a
specific resource version (causing the operation fail, if that number has
advanced).
This make it quite simple to implement a lock mechanism on top of any
kubernetes resource. And we have at least two cases where this is used to
implement things like "leader election":
1) in camel-kubernetes
2) in spring-cloud-kubernetes
So, that would require some coding, but its nothing we've never done before.
We could use that for some cron tasks as well as cluster unique tasks like schema generation or data load
Quoting Ioannis Kanellos
We could use that for some cron tasks as well as cluster unique tasks like schema generation or data load