Advanced Topics - Leader Election in case of multiple replicas triggered for High Availability purposes #6612
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
I think it would be good to add, to the Leader election section, the use-case about running several instance of the custom controller workload/pod (i.e., only one being 'active') in order to increase the High Availability characteristics of your operator's controller (so the operator deployer has higher control on how fast a "blocked" currently 'active' controller instance is being replaced by another running (but not yet 'active') instance.
Adding this HA related use-case to the one currently described (related to a Deployment upgrade where new and old pod instance are running in parallel) would better show where this leader election support from Operator SDK can be used.
The text was updated successfully, but these errors were encountered: