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

Devops 650 allow multiple updates of same resource #16

Merged
merged 3 commits into from
Jan 3, 2018

Conversation

jchanam
Copy link
Collaborator

@jchanam jchanam commented Jan 2, 2018

We have changed the way updates are done.

Until now, when the Redis statefulset was updated, it waited until the rolling update to be finished. The same happened with Sentinel with its deployment.

He have multiple premises in mind:

  • Kubernetes deployments and statefulsets are trustworthly.
  • Multiple updates on the same resource on k8s can be made.
  • We don't want to update sentinel and redis at the same time to avoid failures.

So, from now, the updates don't wait to themselves to be finished. In stead, they check that the other resource is ready and there's no an update being done (to prevent simultaneous redis and sentinel updates).

@jchanam jchanam requested a review from a team January 2, 2018 16:42
@jchanam jchanam added the blocked label Jan 2, 2018
@jchanam jchanam removed the blocked label Jan 3, 2018
@jchanam jchanam merged commit bcf9b3a into master Jan 3, 2018
@jchanam jchanam deleted the devops-650-allow-multiple-updates-of-same-resource branch January 3, 2018 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants