Freeze for 2+ operators of the same priority

[kopf-archiver]

An issue by nolar at 2019-04-30 09:26:15+00:00
Original URL: zalando-incubator/kopf#51
 

Current Behaviour

When 2+ operators with the same priority run (e.g. default of 0), both are working. Which breaks the purpose of the peering to prevent duplicated side-effects.

Expected Behaviour

When 2+ operators with the same priority run, with peering configured and functional, only one should be functioning, others should freeze.

The best case would be that all operators issue a warning and freeze, so that the cluster becomes not served anymore — this will bring people attention sooner than if they negotiate which one should work. 2+ operators with the same priority is obviously a deployment error.

Note: If the operators make a decision on which one runs, which one freezes (e.g. by the most recent pod start time, or by id, or anything else comparable), then it could happen that the old deployment in another namespace serves the cluster, when a new operator is expected to work. It is better to stop serving and bring people attention to resolve the situation.

Suggestion

See the module where it all happens.

Checklist

• Implementation.
• Tests — manually (there is no auto-tests for peering yet).
• Documentation (in docs/peering.rst)

---

Commented by smileisak at 2019-06-08 19:29:16+00:00
 

nolar is this issue is already treated ?

---

Commented by nolar at 2019-06-10 12:16:16+00:00
 

smileisak To my knowledge, no, it is free and waiting.