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.

Sign up for GitHub

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

FAQ:Zero downtime images #397

Closed
wants to merge 2 commits into from
Closed

FAQ:Zero downtime images #397

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
89b84a9
add FAQ:Zero downtime images
drnickiw Feb 20, 2019
227dbb6
update FAQ:Zero downtime images
drnickiw Feb 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions content/faq/how-achieve-zero-downtime-image.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
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.