forked from elmoallistair/juaragcp
-
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.
Merge pull request elmoallistair#1 from gabrielhozana/gabrielhozana-p…
…atch1 Create readme.md
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
23 changes: 23 additions & 0 deletions
23
labs/gsp343_optimize-costs-for-google-kubernetes-engine-challenge-lab/readme.md
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,23 @@ | ||
# [Optimize Costs for Google Kubernetes Engine: Challenge Lab ](https://www.qwiklabs.com/focuses/16327?parent=catalog) | ||
|
||
## Topics tested: | ||
|
||
In this challenge lab you will be assessed on your knowledge of the following areas: | ||
* Deploying an app on a multi-tenant cluster | ||
* Migrating cluster workloads to an optimized node pool | ||
* Rolling out an application update while maintaining cluster availability | ||
* Cluster and pod autoscaling | ||
|
||
## Challenge scenario | ||
|
||
You are the lead Google Kubernetes Engine admin on a team that manages the online shop for OnlineBoutique. | ||
|
||
You are ready to deploy your team's site to Google Kubernetes Engine but you are still looking for ways to make sure that you're able to keep costs down and performance up. | ||
|
||
You will be responsible for deploying the OnlineBoutique app to GKE and making some configuration changes that have been recommended for cost optimization. | ||
|
||
Here are some guidelines you've been requested to follow when deploying: | ||
* Create the cluster in the us-central1 region | ||
* The naming scheme is team-resource, e.g. a cluster could be named onlineboutique-cluster | ||
* For your initial cluster, start with machine size n1-standard-2 (2 vCPU, 8G memory) | ||
|