forked from cloudposse/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FAQ:Zero downtime images cloudposse#397
- Loading branch information
1 parent
161df17
commit b2c0aa7
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
title: "How do we achieve image updates with zero downtime?" | ||
description: "This is similar to scaling a cluster vertically." | ||
tags: | ||
- VM | ||
- image | ||
- kops | ||
- updates | ||
--- | ||
|
||
## Question | ||
|
||
How do we achieve zero-downtime deploys of VM image updates? | ||
|
||
|
||
## Answer | ||
|
||
This is similar to scaling a cluster vertically. This can be done with zero downtime. | ||
|
||
Basically, it requires setting the `KOPS_BASE_IMAGE` env to the new value, rebuilding the `kops` manifest, then redeploying by running the `kops rolling-update` command. See [here.](https://github.com/cloudposse/geodesic/blob/master/rootfs/templates/kops/default.yaml#L171) | ||
|
||
Our instructions are [here.](https://docs.cloudposse.com/kubernetes-optimization/scale-cluster-vertically/) | ||
|
||
We don’t presently build the `kops` images. Using Packer would be the strategy we would take. | ||
|