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 high-availability #155

Merged
merged 1 commit into from
Jun 6, 2018
Merged

Operator high-availability #155

merged 1 commit into from
Jun 6, 2018

Conversation

ewoutp
Copy link
Contributor

@ewoutp ewoutp commented Jun 5, 2018

This PR sets the number of replicas for the all operator to 2 (from 1). This ensures that 1 replica is always standing by (waiting in leader election) and able to take over quickly when the leader is not responding.
This is faster than waiting for kubernetes to terminate a pod that becomes unresponsive.

This PR also adds tolerations that were still missing on the deployment-replication operator.

@@ -5,7 +5,7 @@ metadata:
name: {{ .DeploymentReplication.OperatorDeploymentName }}
namespace: {{ .DeploymentReplication.Operator.Namespace }}
spec:
replicas: 1
replicas: 2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

personal curiosity: why 2 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So 1 can fail. Could be 3, but IMO 2 would make a good default (note that this deployment can be fully customized by customer if they want to)

@ewoutp ewoutp merged commit 659c5c9 into master Jun 6, 2018
@ewoutp ewoutp deleted the feature/operator-ha branch June 6, 2018 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants