-
Notifications
You must be signed in to change notification settings - Fork 424
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Demo week 3: Proposal - Deployment and rollbacks with Kubernetes (#2415)
- Loading branch information
1 parent
bc28c0f
commit 2f8c43e
Showing
1 changed file
with
30 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,30 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Deployment and rollbacks with Kubernetes | ||
|
||
## Names and KTH ID | ||
|
||
- Robin Claesson ([email protected]) | ||
- Simon Hocker ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 3 | ||
|
||
## Category | ||
|
||
- Demo | ||
|
||
## Description | ||
|
||
We want to give a demo for how you can configure a Kubernetes cluster. We will start with giving a short introduction into the world of microservice and container architecture, then dive straight into Kubernetes and its purposes. | ||
|
||
We will then begin the demo by showing a configuration file for a Kubernetes cluster, and then start it up, showing how the cluster represents the configuration. Following that, we demonstrate how to increase the replicas of a pod to scale with demand. | ||
|
||
We will then update the configuration to change the version of one of the pods and show how the cluster is updated. This new version will contain a bug, and to fix this we will show how to use the rollback feature of Kubernetes to go back to the previous working version, then deploy a corrected version without the bug. | ||
|
||
**Relevance** | ||
|
||
Kubernetes a modern system for deploying containers in a micro service architecture. As applications grew to hold many complex containers across numerous servers, the system would become too complex for mainstream services to keep up. Problems arose consisting of how to coordinate, schedule and communicate between such an abundance of containers, how to scale them, etc. Google introduced Kubernetes to solve these problems. |