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

Rolling deployment #753

Merged
merged 2 commits into from
Sep 3, 2024
Merged

Rolling deployment #753

merged 2 commits into from
Sep 3, 2024

Conversation

MatMoore
Copy link
Contributor

@MatMoore MatMoore commented Sep 3, 2024

In preparation for implementing horizontal pod autoscaling, enable multiple replicas and a rolling update deployment strategy.

https://user-guide.cloud-platform.service.justice.gov.uk/documentation/concepts/deploying.html#deploying-to-the-cloud-platform

This allows the extra replica to handle traffic if a worker node dies.

This may need to be bumped up again for production, but let's start
with 2 as a baseline.

https://user-guide.cloud-platform.service.justice.gov.uk/documentation/concepts/deploying.html#multiple-replicas
rollingUpdate (the default deployment strategy) means that when your
deployment is updated, or your pods need to be moved to another node,
the cluster will create new instances before terminating the old ones.
maxSurge: 100% means that a complete additional copy of your deployment
will be created before any of your old pods are terminated, and
maxUnavailable: 50% means the cluster will only allow at most half of
your pods being unavailable (e.g. if the new version of your service
fails to deploy, for some reason).

https://user-guide.cloud-platform.service.justice.gov.uk/documentation/concepts/deploying.html#zero-downtime-deploys
@MatMoore MatMoore merged commit 59b3f10 into main Sep 3, 2024
8 checks passed
@MatMoore MatMoore deleted the rolling-deployment branch September 3, 2024 12:30
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