operator-framework
Update golang Operator docs for "Advanced Topics - Leader Election - Leader-with-lease"
The docs for building golang operators have a section describing how to configure leader election. Under the default leader-with-lease option, the docs mention:
When the operator is not running in a cluster, the Manager will return an error on starting since it can’t detect the operator’s namespace in order to create the configmap for leader election
But rather than using ConfigMap as a lock, the current version of the SDK seems to be using Kubernetes leases. I can update the docs to mentioned that, if I'm understanding things correctly.
I looked through the other issues related to Leader Election briefly, and it seemed like they were all about changing behavior or updating the Docs for Leader-for-life.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale