Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operator multiple replicas #252

Closed
wonderhoss opened this issue Mar 26, 2020 · 3 comments
Closed

Operator multiple replicas #252

wonderhoss opened this issue Mar 26, 2020 · 3 comments
Labels

Comments

@wonderhoss
Copy link

Expected behaviour

redis-operator helm chart and example Deployment should either
a) use more than one replica
or
b) have documentation indicating that a single-replica Deployment is strictly required

Actual behaviour

Both helm chart and example YAML have a hard coded replicas: 1 without the documentation specifying whether this is a functional requirement or not.

Background

We tend to deploy operators and controllers as pairs of two (or more) replicase so that there is no gap in coverage when losing or replacing the node running the operator Pod.
The use of a hard-coded replicas: 1 in the helm chart along with a lack of leadership-election settings makes me suspect that the redis-operator currently can only run as a single-replica deployment, but can't verify either way.

@github-actions
Copy link

This issue is stale because it has been open for 45 days with no activity.

@github-actions github-actions bot added the stale label Jan 14, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@Wouter0100
Copy link
Contributor

Leader election was introduced in #438. I updated the Helm chart in #492.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants