add leader election and multi replica support #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds full leader election and multi replica support to the operator. This is a requirement for resiliency through a PDB and is needed as clusters move towards more automatic upgrade scenarios. A PDB + multiple replicas is the best way to ensure the operator continues to function after a cluster upgrade (and really throughout all scenarios).
You can see below how this is an active-passive HA model where only the replica with the leader election lock performs actions.

Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested locally + e2e. This change is really just taking advantage of built-in controller runtime features which is a well tested and well established k8s library.
Checklist: