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.
Introduces support for leader election between multiple replicas of the Operator pod.
Now we pass the name of the pod to each operator pod and start with
2 replicas
by default, using kubernetes lock leases it then elects a leader, which then patches the pod so that now the operator service only hits that pod (the leader)We have the requirement to have a single pod serve as the operator API due to the fact that when we are doing online update, the MinIO pods will attempt to download their binary from the operator pod via the operator service, so a single pod should host the downloaded file.
Signed-off-by: Daniel Valdivia 18384552+dvaldivia@users.noreply.github.com